| Re: [4diac-dev] 回复: Foundation Code and Issue services reminder |
|
Hi, Locating the source code on Github does not ensure more contributions. Same holds true for Sourceforge, which was THE BIG THING long
before GitHub I have a different project there, so I have some experience in that
😃 GitHub and GitLab offer a quite similar set of features, but using dedicated Eclipse infrastructure will most likely make the work of
contributors and project lead easier, than also dealing with a third involved party (GitHub/Microsoft) in case of troubles. My 2 cents on that. Best regards, Martin -------------------------------------------------- Dipl.-Ing. Martin Melik-Merkumians Advanced Mechatronic Systems Automation and Control Institute (ACIN) TU Wien DVR-Number: 0005886 Gusshausstr.
27-29, room CD-04-24 1040 Vienna, Austria Phone: +43 (0)1 588 01 37688 Fax: +43 (0)1 588 01 937688 Email:
melik-merkumians@xxxxxxxxxxxxxxxxx -------------------------------------------------- Von: 4diac-dev <4diac-dev-bounces@xxxxxxxxxxx>
Im Auftrag von zhaoxin@xxxxxxxxxxxxxxxxx Yes, I agree with Fabio. Regards Tibalt 发件人:
4diac-dev-bounces@xxxxxxxxxxx <4diac-dev-bounces@xxxxxxxxxxx>
代表
Fabio Gandolfi Hi all,
In my opinion if you want more people to contribute on 4diac as a open source project Github is the way to go because it has a big open source community.
Best regards,
>
> the long anticipated step of migrating from the current setup to a more modern is now here. Both options have quite some advantages.
>
> As I'm happy with both options I wanted to ask you the 4diac community what option you would prefer?
>
> Cheers,
> Alois
>
>
> On Mon, 2022-03-14 at 10:25 -0400, 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/
>> _______________________________________________
>> 4diac-dev mailing list
>> 4diac-dev@xxxxxxxxxxx
>> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/4diac-dev
|