[nebula-dev] Github issues or Bugzilla's

[Wim Jongman]

Hi,

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.

Cheers,

Wim

[Jonah Graham]

+1 for going all the way to GitHub, Issues included.

What about the Wiki? Want to move that too?
https://github.com/eclipse/nebula/wiki

Jonah

~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com

Post by Wim Jongman
Hi,
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.
Cheers,
Wim
_______________________________________________
nebula-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

[Laurent Caron]

Hi,

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.

Laurent

Post by Jonah Graham
+1 for going all the way to GitHub, Issues included.
What about the Wiki? Want to move that too?
https://github.com/eclipse/nebula/wiki
Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com

Post by Wim Jongman
Hi,
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.
Cheers,
Wim
_______________________________________________
nebula-dev mailing list
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
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

[Wim Jongman]

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-***@eclipse.org [mailto:nebula-dev-***@eclipse.org] On Behalf Of Laurent Caron
Sent: Monday, 20 August 2018 18:09
To: Nebula Dev
Subject: Re: [nebula-dev] Github issues or Bugzilla's

Hi,

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.

Laurent

Le sam. 18 août 2018 à 16:18, Jonah Graham <***@kichwacoders.com<mailto:***@kichwacoders.com>> a écrit :
+1 for going all the way to GitHub, Issues included.

What about the Wiki? Want to move that too? https://github.com/eclipse/nebula/wiki

Jonah

~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com<http://www.kichwacoders.com>


On Sat, 18 Aug 2018 at 15:09, Wim Jongman <***@gmail.com<mailto:***@gmail.com>> wrote:
Hi,

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.

Cheers,

Wim

_______________________________________________
nebula-dev mailing list
nebula-***@eclipse.org<mailto:nebula-***@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-***@eclipse.org<mailto:nebula-***@eclipse.org>
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

[Jonah Graham]

I think avoid 2 of anything if possible. Either request ***@eclipse
to disable the Wiki, or add a single page redirecting people to the Eclipse
wiki.


~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com

Post by Wim Jongman
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
*Sent:* Monday, 20 August 2018 18:09
*To:* Nebula Dev
*Subject:* Re: [nebula-dev] Github issues or Bugzilla's
Hi,
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.
Laurent
+1 for going all the way to GitHub, Issues included.
What about the Wiki? Want to move that too?
https://github.com/eclipse/nebula/wiki
Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com
Hi,
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.
Cheers,
Wim
_______________________________________________
nebula-dev mailing list
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
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
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

[Dunne (US), Donald G]

Either is fine with me.

From: nebula-dev-***@eclipse.org [mailto:nebula-dev-***@eclipse.org] On Behalf Of Wim Jongman
Sent: Saturday, August 18, 2018 7:10 AM
To: Nebula Dev <nebula-***@eclipse.org>
Subject: [nebula-dev] Github issues or Bugzilla's

Hi,

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.

Cheers,

Wim

[Mickael Istria]

I would like to suggest another alternative: get rid of the wiki and embed
documentation inside the repo with source code?

[Wim Jongman]

Can you elaborate on that a little bit Mickael?

From: nebula-dev-***@eclipse.org [mailto:nebula-dev-***@eclipse.org] On Behalf Of Mickael Istria
Sent: Monday, 20 August 2018 22:16
To: Nebula Dev
Subject: Re: [nebula-dev] Github issues or Bugzilla's

I would like to suggest another alternative: get rid of the wiki and embed documentation inside the repo with source code?

[Mickael Istria]

I suggest that instead of a wiki, the documentation gets into the main repo
in a "documentation" folder, as .mediawiki and/or as .md and/as .adoc
files. together with the source code. I think this allows a better
synchronization of source vs doc as it's possible to say on a Gerrit patch
or PR "Please update file xyz.adoc" at the same time. It also allows to
track contributors to documentation as code contributors, reflected in the
same Git history, facilitating inclusion of doc related changes in N&N,
which is relatively fair.
Since GitHub provides an "edit" button which automatically starts a PR and
has a good preview for doc files, it is as simple to contribute to doc in
the GitHub repo than it is the contribute directly to a wiki. It also
allows to enforce review which ultimately lead to more awareness from
committers about what needs to be documented (leading to ideas of
improvements) and improve quality of the documentation (preventing
erroneous statements in documentation).

Cheers

[Wim Jongman]

Brilliant, that sounds really professional.

From: nebula-dev-***@eclipse.org [mailto:nebula-dev-***@eclipse.org] On Behalf Of Mickael Istria
Sent: Tuesday, 21 August 2018 09:07
To: Nebula Dev
Subject: Re: [nebula-dev] Github issues or Bugzilla's

I suggest that instead of a wiki, the documentation gets into the main repo in a "documentation" folder, as .mediawiki and/or as .md and/as .adoc files. together with the source code. I think this allows a better synchronization of source vs doc as it's possible to say on a Gerrit patch or PR "Please update file xyz.adoc" at the same time. It also allows to track contributors to documentation as code contributors, reflected in the same Git history, facilitating inclusion of doc related changes in N&N, which is relatively fair.
Since GitHub provides an "edit" button which automatically starts a PR and has a good preview for doc files, it is as simple to contribute to doc in the GitHub repo than it is the contribute directly to a wiki. It also allows to enforce review which ultimately lead to more awareness from committers about what needs to be documented (leading to ideas of improvements) and improve quality of the documentation (preventing erroneous statements in documentation).

Cheers