>>>>...then I did a GitHub PR directly and after confirmation that the fix >>>> works I pushed directly in the repo. JIRA was not involved at all. >>>>A situation I hope won't continue given the current contribution >>> guidelines! ;-) >>>Assuming the guidelines are these >>https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681408 >> I don't see a must next to creating an issue. >>"And remember: These are guidelines, not laws." >>Indeed. >> > > Yes, agreed, these are guidelines, and there will always be exceptions. > But having guidelines that don't reflect common practice is also > pointless. So, if that's the case, change the guidelines!
... but what I did was not an exception! The way I see it I had been following the guidelines intuitively so... they must be reasonable enough right now. Why would they need to be changed? Because JIRA is not mandatory? > I also agree with Gili that if JIRA is going to useful, in particular if > it's to be a canonical record in future, then we need to have and follow > general guidelines on what has to go in it and not. JIRA is *a* canonical record but not *the* canonical record. The charts will be a bit harder to generate, but... it happens. I consider the mailing list a more important record, but I also don't see it the only place the action happens. Some contributors, for example, might prefer to use only the GitHub interface (which will only email notifications on the mailing list for archival purposes). You will not produce contributions by making the perfect guidelines. You need people! If anything, the thicker the guidelines the more people will be put off by it. --emi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
