Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add contributors to release note #6297

Closed
fpetrakov opened this issue Aug 22, 2022 · 5 comments
Closed

Add contributors to release note #6297

fpetrakov opened this issue Aug 22, 2022 · 5 comments

Comments

@fpetrakov
Copy link
Contributor

fpetrakov commented Aug 22, 2022

Hi, I suggest adding 'Contributors' section to release note. I think this way more people will not only become but also stay as contributors to Stylelint. It's just a nice and a kind of warm feeling to see own nickname and profile picture in release note of the project.

image

@fpetrakov fpetrakov changed the title Add contributors to release Add contributors to release note Aug 22, 2022
@JounQin
Copy link
Member

JounQin commented Aug 22, 2022

It will be implemented in next iteration, we have some issues for inconsistent output for now, it will be fixed in next few days.

@JounQin
Copy link
Member

JounQin commented Aug 22, 2022

Besides, @jeddy3 @ybiquitous Shall we enable "discussions" for such questions instead of issues?

@ybiquitous
Copy link
Member

ybiquitous commented Aug 22, 2022

It will be implemented in next iteration, we have some issues for inconsistent output for now, it will be fixed in next few days.

This issue sounds like a duplicate of #6253.

Shall we enable "discussions" for such questions instead of issues?

Yes, of course. Please see also Managing issues.

@jeddy3
Copy link
Member

jeddy3 commented Aug 23, 2022

@fpetrakov Thanks for the suggestion.

Shall we enable "discussions" for such questions instead of issues?

Issues and StackOverflow are working well for us, including choosing a template. These types of questions are rare and could easily fall under the request a new feature template. I don't think it makes sense introduce another comms channel to manage as I suspect some users will start adding feature requests or requests for support there, causing a split.

This issue sounds like a duplicate of #6253.

Yes, we can close in favour of that issue.

@jeddy3 jeddy3 closed this as completed Aug 23, 2022
@ybiquitous
Copy link
Member

Yes, of course. Please see also Managing issues.

Oh, I completely misunderstood it. Sorry for any confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants