I would like to keep the wiki. It’s the central source of eclipse information. I don’t want the users to be looking in two places and I am not looking forward
to maintain two wikis.
Maybe a Jenkins job that converts mediawiki to markdown for selected pages, and check it into the nebula wiki (which is a git repo)?
Cheers,
Wim
From: nebula-dev-bounces@xxxxxxxxxxx [mailto:nebula-dev-bounces@xxxxxxxxxxx]
On Behalf Of Laurent Caron
Sent: Monday, 20 August 2018 18:09
To: Nebula Dev
Subject: Re: [nebula-dev] Github issues or Bugzilla's
I think that Github bug tracker is less powerful than bugzilla, but it's easier to use and sufficient for commons tasks, so +1 for Github Issues.
And I'll follow Jonah about the wiki.
+1 for going all the way to GitHub, Issues included.
Any opinions on using bugzilla or githib issues? I thought we decided for Issues but the contributions guide still points to bugzilla. Before I change I want give the opportunity for discussion again.
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
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@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev