>> I think we need to plan a separate contribution workflow without GitHub (see >> my other thread 'How to participate in Apache NetBeans without a GitHub >> account?'). >> Right now we are tied to GitHub and it's impossible to be involved in >> anything without jumping onto GitHub. >> > Not sure if (or why) it is impossible to be involved without GitHub. AFAIK > anyone can subscribe to this mailing list, checkout from the Git repo on > Apache: https://gitbox.apache.org/repos/asf?p=incubator-netbeans.git > and send patches to this mailing list. (Or maybe links to patches, if this > list strips attachments.) > My view is that we are using GitHub because it is more convenient.
[Switching to this thread where we are talking about our workflow] I think there has been 0 patches discussed on the mailing list so far. It's not only convenient, we are totally dependent on GitHub for PRs / code review / comments. I'll start looking into how https://reviews.apache.org/r/ might help one contribute to NetBeans too. --emi ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On 6 June 2018 4:13 PM, Emilian Bold <[email protected]> wrote: > Hello, > > I'm trying to see how one could contribute to NetBeans without a GitHub > account. > > To see what's going on one needs to also subscribe to > [email protected] where messages about new pull requests and > comments are posted. > > PROBLEM 1: There's no way to comment on a PR from the mailing list. In the > email I see this note: > > > This is an automated message from the Apache Git Service. > > > > To respond to the message, please log on GitHub and use the > > > > URL above to go to the specific comment. > > So, we need some robot or something to act as a proxy (we had something like > this for Slack which was commenting on the #netbeans IRC channel) and add our > comments to GitHub too. > > PROBLEM 2: How do I see the PR patch? The notification gives me the PR URL > but I don't see the repository/branched used so I cannot jump into the > terminal to do a `git checkout`. > > Both of these problems belong to Apache Git Services, I'll contact them too. > > Suggestion: It would be good to use https://reviews.apache.org/r/ too, not > GitHub PR exclusively. > > Allowing inclusive ways of contributing is going to be important long-term. > > GitHub should just be one venue where we engage with the community and > contributors but we should have other workflows in place, preferably that > depend on Apache infrastructure only. > > --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 --------------------------------------------------------------------- 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
