Forwarded here from Bugzilla
https://bugs.eclipse.org/bugs/show_bug.cgi?id=552964#c50
> --- Comment #50 from Jonah Graham <jonah@xxxxxxxxxxxxxxxx> ---
> There has been a lot of conversation here, so I summarize my responses. Please
> ask again if there is something else needed.
>
> 1) EPLv2: I will send to mailing list.
ok
Done. See PR 369
> 2) github repo name: If there are multiple (and growing) number of git repos,
> may I suggest we request a top-level org at github instead of eclipse. i.e. the
> same as eclipse-cdt and eclipse-cbi? Then the URL would be (something like):
> https://github.com/eclipse-embed-cdt/eclipse-plugins
> https://github.com/eclipse-embed-cdt/web-jekyll *
Good idea!
I don't know how many repos there will be, but if it is possible to have a separate org, that would be a nice options.
There is another significant advantage of separate org. Travis-CI is limited to 8(?) executors per org. In the past that has meant builds can be delayed by hours to a day on the eclipse main org.
> 3) Renaming plug-ins: Liviu, you went through this before with the migration of
> GNU ARM -> GNU MCU. I don't have any idea what it took to do that work, but
> when the project was first proposed I was quite glad you had once done the
> migration already as I knew it would probably be needed again.
During the previous migration I did not touch any existing package names, class names, or internal ids, since this is a no go from a compatibility point of view.
> 4) Renaming ids: Well this is a lot harder because it breaks existing projects
> and extenders in a much more significant way. AFAICT you maintained the
> pre-existing IDs when you did the ARM -> MCU rename a few years ago and new IDs
> have ilg.gnumcueclipse instead.
Exactly. All existing ids were preserved, and new ids were allocated in the new group.
> *) Note that I would really like to see this published to
> http://eclipse.org/embed-cdt which means it needs to be via
> ssh://committer_id@xxxxxxxxxxxxxxx:29418/www.eclipse.org/embed-cdt.git - I am
> not sure, but I believe this is a requirement.
My understanding is that it is a requirement to commit the html content at that url, and the content will be automatically published to the web server and visible as http://eclipse.org/embed-cdt, which I would also like to use.
The web-jekyll repo contains the editable content of the web site, in markdown, which needs to be processed by jekyll and the html pages be generated.
Jekyll can be executed automatically as a GitHub Action, attached to repo commits. I'm not sure how complicated is to push content to the ssh url from GitHub Actions, but I guess it can be done.
(Now the conversion is performed as a Travis CI task, and the result is pushed on a separate GitHub repo)
Perfect - that sounds ideal and the only thing that needs to change is publishing to the
www.eclipse.org/embed-cdt.git repo instead. Let me know how/if I can help.
> I think it is going to be a
> little complicated, but we can resolve it, as
> https://gnu-mcu-eclipse.github.io/ contains both items moving to embed-cdt and
> items not moving IIUC.
Right, the existing content will have to be reorganised/rewritten, to keep only the Embedded CDT pages; the xPack related pages are already published on https://xpack.github.io
As theme I plan to use the same theme as for the xPack site, but any suggestions are welcome.
Regards,
Liviu
_______________________________________________
embed-cdt-dev mailing list
embed-cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/embed-cdt-dev
