[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jdt-dev] Foundation Code and Issue services reminder
|
> How can I access the new repo using my Eclipse account?
Just a two simple steps:
1) register an account at github with the same e-mail you used for
eclipse (not required but recommended for dinosaurs).
2) add the github username to your existing eclipse account in the user
profile
You have now full committer access to that repository using standard
git-tools.
In general it is advisable to not commit directly to that repository but
do the following:
1) Fork the repository
2) check out the fork
4) create a branch, push your changes and you will get a Link on how to
open a PR
5) after your PR is changed you can simply click "Fetch upstream" to
sync your fork with the main repository.
Github also offers a wiki[1], powerfull issue management [2],
discussions [3] you can even enable webpages [4] and several CI and
management actions [5].
Whenever you have questions there should be someone to help
noob-dinosaurs, even google will answer most of the questions right away
if everyone is asleep...
[1]
https://docs.github.com/en/communities/documenting-your-project-with-wikis/about-wikis
[2] https://github.com/features/issues
[3] https://docs.github.com/en/discussions
[4] https://pages.github.com/
[5] https://github.com/features/actions
Am 15.03.22 um 14:37 schrieb Stephan Herrmann:
I'm following these changes from a distance, and any question/comment I
will make will sound like the voice of dinosaurs at best. Still I will
raise them:
It seems, JDT decided to move to GitHub, not GitLab? When was this
decision made?
How can I access the new repo using my Eclipse account?
I cannot imagine working on JDT without full access to bugzilla. Perhaps
it's lack of imagination, so has anybody penned down a strategy how our
huge knowledge base can be used and maintained past the migration? IMHO
it must be possible to access each existing bug report and extend it
with additional information, as development continues.
What is the plan for migrating JDT's wiki pages?
When I joined the project all the workflows I learned were based on
https://wiki.eclipse.org/JDT_Core_Committer_FAQ -- Over the years I
tried to help keep this document up-to-date (not claiming that it is
fresh and accurate on every detail), but it seems, that document will
fall into oblivion soon. Is there any guide to replace it in the future?
Also this page doesn't look like the project is ready for roll out:
https://wiki.eclipse.org/Platform-releng/Migration_To_GitHub
I have gone through a sufficient number of technology migrations, to
have lost my enthusiasm about chasing for documentation how the basic
steps of development are performed on the new platform. And I don't
think letting everybody figure out on their own will create a coherent
culture.
In plain words: when JDT will be on GitHub I will be a total noob and
could use *a lot* of help :) Is it just me?
In case you like dinosaurs, please feed them to avoid their second
extinction.
best,
Stephan
On 14.03.22 15:25, webmaster@xxxxxxxxxxxxxxxxxxxxxx wrote:
Hi Everyone,
You may not be aware but the Webmaster team has started the process of
deprecating our current Gerrit[1] and Bugzilla[2] instances. We'd like
to encourage your project to discuss moving sooner rather than later
to avoid migrations done against a specific timeline.
Your migration options are either the Foundation’s hosted GitLab
instance [3] or our presence on GitHub[4]. Both options provide a more
integrated tool set (code, issues, wiki and discussions (GitHub only))
rather than our current disparate tool set.
Continuous integration with Jenkins works well for both options, and
will be our focus for the foreseeable future. For GitLab we’re also
investigating the possibilities of using GitLab CI which is similar to
GitHub actions, and could be used for features like dependency checks
or GitLab pages.
You can start your move by filing an issue[5] letting us know where
(GitLab/GitHub) and when you'd like to move, and we'll do our best to
make it happen.
Do you have questions? Check out some of our documentation[6], or a
comparison[7] to help you choose. You can also write to Webmaster, and
our team will do it's best to find an answer.
-Matt.
[1] https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/680
[2] https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/679
[3] https://gitlab.eclipse.org
[4] https://github.com/eclipse
[5] https://gitlab.eclipse.org/eclipsefdn/helpdesk
[6] https://wiki.eclipse.org/Gitlab#Migrating_from_Gerrit_and_Bugzilla
[7] https://spectralops.io/blog/github-vs-gitlab/
_______________________________________________
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