Hey Henne
On Tue, Feb 23, 2016 at 7:46 AM, Henne Vogelsang
Hey Manu,
On 19.02.2016 19:40, Manu Gupta wrote:
1. Really come out of hallway conversations.
I fully agree with this statement. However I have a problem with your definition of 'hallway' :-)
For example, mentoring 101 was practically, started within a few discussions inside a corner,
and was just done. It is great. However, once the development started the discussions (if there were any) should really be done at opensuse-web (all of them).
All of the discussions (except the initial one that Chris/Cornelius/Me wanted to do something for mentoring) happened inside the github project where everyone can participate...
https://github.com/openSUSE/mentoring/issues?q=is%3Aissue+label%3AAdministra...
Agreed.
This goes to OSEM
OSEM is another example where everything happens publicly in the github project
https://github.com/openSUSE/osem
in the IRC channel
irc://freenode.net#osem
and on opensuse-web.
Yup, I can see that now. I checked osem.io a couple of months back and it did not have opensuse-web on it.
2. Send commit messages to the relevant mailing list.
3. Send new bugs that are created to the relevant mailing lists.
If you want notifications about stuff happening in some openSUSE repository on github use the notifications of github. BTW this is what developers already do! New developers hang out on github and we need to draw them in there, not on some openSUSE mailing list :-)
Yes and I cannot agree more. It is not about me here :). It is about what concrete steps can we take that can increase our reach to other contributors(not just developers). It is also about considering that in search of new contributors, are we ignoring older contributors and how do we make a proper trade-off between the two? If I have to evaluate my own suggestions or any other suggestion, I will evaluate them on these metrics 1. Are there any potential side effects in taking these steps? 2. In the long term, do they drive people away from our development repositories or drive them towards it? 3. Is the communication better, and more transparent if we take these steps? 4. Is it more inclusive for old and new contributors? 5. If there is a project wide change to be made, who are the decision makers, is it the people who write code or is it everyone who has contributed to the project in one way or the other? 6. How can you make sure you can reach out to most of them (if not everyone) who has contributed (not just code here, feedback, bugs, marketing, outreach, news etc.) in the project? 7. How can you make sure that the decisions surrounding these projects are in a persistent archive? (One reason I feel that conferences are a great place to start discussions, but not decisions, the same goes for IRCs too) What do you think of these metrics, and how can we point 2 & 3, stand on that metric or any other measure that we can take to improve the current scenario? If proposals are doable (if someone volunteers to do it), and if we think a particular suggestion stands well on the above metrics, I think we should go for it.
Henne
-- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
-- Regards Manu Gupta -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org