Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] Moving project to GitHub
Thank You!

I updated README and CONTRIBUTING files. 3 new stars in meantime :P

On 12 May 2020 at 20:44:37, Basil Mohamed Gohar (basilgohar@xxxxxxxxxxxx) wrote:


:-)

I hope this can garner some more positive attention for the project.

On Tue, May 12, 2020 at 11:36 am, Dawid Pakuła <zulus@xxxxxxxxx> wrote:
So, we are now on GitHub ;)

Repository: https://github.com/eclipse/pdt I already prepared basic GitHub workflow for tests. This job package and archive unsigned eclipse repository. 
Feel free to watch, star, fork and pull request ;) 

Some things still have to be done in near future:
1. Issue templates
2. Readme/contribution/wiki updates
3. Tweak issue labels
4. Probably re-think commit message requirements ("#num - something" rather than "Bug num - something”)

On 8 May 2020 at 13:14:57, Dawid Pakuła (zulus@xxxxxxxxx) wrote:

Hi,

I prepared bug 562928 [1]. 

Before move we have to clean-up Gerri to make sure nothing will be loosed.
Unfortunately we will lost currently created bugs (they will not be transferred). ~1/5  of them (113) was created by me and I live with that. I hope others also, it will be fresh start ;)



On 7 May 2020 at 16:36:52, Dawid Pakuła (zulus@xxxxxxxxx) wrote:

Hi,

Small comment about CI/CD. I think we can use travis and/or GitHub actions for fast verification, mostly because its just “mvn verify” calls.
But to prepare signed releases and snapshots we still need foundation hosted Jenkins.

Thanks for feedback! I´ll start migration process as soon as possible. 

In past I had hope for planned foundation gitlab installation [1] but it will require foundation account from user, same as on bugzilla and wiki.

On 5 May 2020 at 08:19:12, Michele Locati (michele@xxxxxxxxx) wrote:

It's a great move for me too!

About continuous integration: I'd use GitHub Actions instead of TravisCI as well. They are much faster and have higher limits (see https://help.github.com/en/actions/getting-started-with-github-actions/about-github-actions#usage-limits ).

--
Michele

Il Lun 4 Mag 2020, 23:45 Dawid Pakuła <zulus@xxxxxxxxx> ha scritto:
Hi Team,

As I mentioned in past, we have to push project forward. Since we lost support from Zend we have to find more contributors (commiters, testers, etc..).
In long term, I and Thierry can´t be only developers. 

I believe that most of PHP developers currently have account in GitHub:
1. Symfony Framework / Symfony Libraries
2. Zend Framework / Laminess
3. Laravel
4. Prestashop
5. Magento
6. PHPUnit
7. Most composer libs

So I want move our project to GitHub also:

1. We can use travis for path-builds
2. Github branch/pull-request rather than Gerrit path set
3. One-commit - one-feature can be achieved via force push on feature_branch

I hope this will allow us to reach new people.

Any thoughts/objections. If not I´d like to start migrations process after two weeks.

_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/pdt-dev
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/pdt-dev
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/pdt-dev

Back to the top