[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jdt-dev] Wikis on jdt Repos?
|
Note that this repo probably doesn't trigger builds I assume:
https://github.com/eclipse-jdt/.github
It has a wiki link:
https://github.com/eclipse-jdt/.github/wiki
But that redirects back to the repo link so I guess that means
it's disabled.
On 10.05.2022 10:21, Andrey Loskutov
wrote:
Please note, that every PR on master with trivial doc
change will trigger JDT Jenkins build, and that will load
Jenkins for 1/2 hour at least.
This is not needed but will disturb others (assuming others
are active at same time) because Jenkins instances aren't
unlimited.
Also it will spam main repo git log (there are people
trying to use it time to time to track regressions etc).
What is wrong with github default wiki?
------ Original Message ------
Sent: 10/05/2022 09:30:56
Subject: Re: [jdt-dev] Wikis on jdt Repos?
I was wondering where we should put
internal process documentation like how to
do triaging.
What about having them in the repo together
with the code, in a dedicated "development-doc"
or "contributing" folder or something like that?
It gives the benefit that it's easier to keep
things sync'd with the actual payload, is easier
to track contributions to the doc/process just
like contribution to the code, and prevent from
multiplying the entry points.
This is what we do on all other Eclipse
projects I'm working on, and so far no concern
was raised.
That's the alternative,
basically. Have a "docs" or "process" folder?
/Thomas
_______________________________________________ jdt-dev
mailing list
jdt-dev@xxxxxxxxxxx To unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/jdt-dev
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev