Hi, I think the natural thing is to use Github issues, but I am happy with whatever works best. Maybe we can leave both channels open for now and see what happens. I suggest to update the controbution guide and website to github issues.
| I recommend checking/requesting protected master branch status -- of course there are more options on protected branches that can be considered, like required PR reviews, passing CI checks, etc. Yes, I agree to block force push to master. The other options you mention seem sensible as well. If hooking into jenkins proves to be difficult then we can also consider travis. Cheers, Wim On Mon, Aug 6, 2018 at 2:40 PM Jonah Graham <jo...@kichwacoders.com> wrote: > Hi Wim, > > Thanks for this. I am now working on updating [3]. I do have some > questions: > > - is the project continuing to use Bugzilla, or are we migrating to GitHub > Issues too. The bug [2] doesn't say either way. I believe if you have > access to Settings (which normal committers don't) you can just turn Issues > off. There is an Eclipse bot that adds links to PRs if you type Bug 123456. > - In past experience setting up github projects at Eclipse the branches > were not protected by default, meaning any committer can force push to > master. I recommend checking/requesting protected master branch status -- > of course there are more options on protected branches that can be > considered, like required PR reviews, passing CI checks, etc. > > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=537191 > [3] https://wiki.eclipse.org/Nebula/Contributions > > Thanks > Jonah > > ~~~ > Jonah Graham > Kichwa Coders Ltd. > www.kichwacoders.com > > > On Mon, 6 Aug 2018 at 11:59, Wim Jongman <wim.jong...@gmail.com> wrote: > >> Hi, >> >> Our Github repo is live and we have received our first pull request for >> XViewer [0] >> >> I'm on vacation but I managed to get the main infrastructure running. >> >> * Main build [1] >> * Pull request build [2] >> >> The following things need to happen >> >> * Accept your github invitation >> * Update the incubation jobs the same way we did for the stable jobs* >> * Update our contribution guide [3] >> * Update our website >> >> If you want to work on any of these items, please go ahead. If you don't >> know how, or want to discuss: I am available to answer e-mails. >> >> Cheers, >> >> Wim >> >> [4] https://www.eclipse.org/nebula/ >> [3] https://wiki.eclipse.org/Nebula/Contributions >> [2] https://hudson.eclipse.org/nebula/job/nebula.stable.pullrequests/ >> [1] https://hudson.eclipse.org/nebula/job/nebula.stable/] >> [0] https://github.com/orgs/eclipse/teams/eclipse-nebula >> >> >> >> * stable widgets are the ones that we release, incubation widgets are >> unstable or unmaintained. >> _______________________________________________ >> nebula-dev mailing list >> nebula-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/nebula-dev > > _______________________________________________ > nebula-dev mailing list > nebula-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/nebula-dev
_______________________________________________ nebula-dev mailing list nebula-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/nebula-dev
