committer += gintas

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

committer += gintas

Jan Matèrne (jhm)
I recognize that the contributor [1] page is not listing Gintas.

@Gintas: Could you add yourself to the source file [2] in the SVN repo for
the website [3], run the build and commit it back, please?

 

Jan

 

 

[1] http://ant.apache.org/contributors.html

[2] https://svn.apache.org/repos/asf/ant/site/ant/sources/contributors.xml

    //section[name="Committers"]/subsection[name="Active Committers"]

[3] https://svn.apache.org/repos/asf/ant/site/

 

Reply | Threaded
Open this post in threaded view
|

Re: committer += gintas

Gintautas Grigelionis
I was deferring that on purpose :-) see my previous e-mails regarding
FishEye links or "Related Projects".
Any chance of splitting of site sources to Git and using SVN for
publication only?

Gintas

2018-02-26 8:10 GMT+01:00 Jan Matèrne (jhm) <[hidden email]>:

> I recognize that the contributor [1] page is not listing Gintas.
>
> @Gintas: Could you add yourself to the source file [2] in the SVN repo for
> the website [3], run the build and commit it back, please?
>
>
>
> Jan
>
>
>
>
>
> [1] http://ant.apache.org/contributors.html
>
> [2] https://svn.apache.org/repos/asf/ant/site/ant/sources/contributors.xml
>
>     //section[name="Committers"]/subsection[name="Active Committers"]
>
> [3] https://svn.apache.org/repos/asf/ant/site/
>
>
>
>
Reply | Threaded
Open this post in threaded view
|

AW: committer += gintas

Jan Matèrne (jhm)
It seems that having the site in git is possible [1]:
- have your site in a git repo
- open a INFRA Jira-Ticket
- branch "asf-site" will be published

We have 7 svn repos [2], most inactive (migrated to git), 1 active and 1 not used for a longer time:
- antlibs, inactive repo, last change 2015, all migrated to git
- build, inactive repo, last change 2007, not used any more (I think)
- core, inactive repo, last change 2015, migrated to git
- easyant, inactive project
- ivy, inactive repo, last change 2015, migrated to git
? sandbox, unknown status, last change 2015, playground for ideas
+ site, active, last change 2weeks ago, website hosting

If we want to migrate the site repo, we should also think about handling the sandbox.

For the meantime I could add your name to the site.
Do you have some text I should add?


Jan


[1] https://blogs.apache.org/infra/entry/git_based_websites_available
[2] https://svn.apache.org/viewvc/ant/




> -----Ursprüngliche Nachricht-----
> Von: Gintautas Grigelionis [mailto:[hidden email]]
> Gesendet: Montag, 26. Februar 2018 09:46
> An: Ant Developers List
> Betreff: Re: committer += gintas
>
> I was deferring that on purpose :-) see my previous e-mails regarding
> FishEye links or "Related Projects".
> Any chance of splitting of site sources to Git and using SVN for
> publication only?
>
> Gintas
>
> 2018-02-26 8:10 GMT+01:00 Jan Matèrne (jhm) <[hidden email]>:
>
> > I recognize that the contributor [1] page is not listing Gintas.
> >
> > @Gintas: Could you add yourself to the source file [2] in the SVN
> repo
> > for the website [3], run the build and commit it back, please?
> >
> >
> >
> > Jan
> >
> >
> >
> >
> >
> > [1] http://ant.apache.org/contributors.html
> >
> > [2]
> >
> https://svn.apache.org/repos/asf/ant/site/ant/sources/contributors.xml
> >
> >     //section[name="Committers"]/subsection[name="Active Committers"]
> >
> > [3] https://svn.apache.org/repos/asf/ant/site/
> >
> >
> >
> >


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AW: committer += gintas

Gintautas Grigelionis
What I meant is that there are more changes that I've queued up (check out
the fresh revision of Ant manual ;-)

Gintas

Den 28 feb. 2018 08:58 skrev "Jan Matèrne (jhm)" <[hidden email]>:

> It seems that having the site in git is possible [1]:
> - have your site in a git repo
> - open a INFRA Jira-Ticket
> - branch "asf-site" will be published
>
> We have 7 svn repos [2], most inactive (migrated to git), 1 active and 1
> not used for a longer time:
> - antlibs, inactive repo, last change 2015, all migrated to git
> - build, inactive repo, last change 2007, not used any more (I think)
> - core, inactive repo, last change 2015, migrated to git
> - easyant, inactive project
> - ivy, inactive repo, last change 2015, migrated to git
> ? sandbox, unknown status, last change 2015, playground for ideas
> + site, active, last change 2weeks ago, website hosting
>
> If we want to migrate the site repo, we should also think about handling
> the sandbox.
>
> For the meantime I could add your name to the site.
> Do you have some text I should add?
>
>
> Jan
>
>
> [1] https://blogs.apache.org/infra/entry/git_based_websites_available
> [2] https://svn.apache.org/viewvc/ant/
>
>
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Gintautas Grigelionis [mailto:[hidden email]]
> > Gesendet: Montag, 26. Februar 2018 09:46
> > An: Ant Developers List
> > Betreff: Re: committer += gintas
> >
> > I was deferring that on purpose :-) see my previous e-mails regarding
> > FishEye links or "Related Projects".
> > Any chance of splitting of site sources to Git and using SVN for
> > publication only?
> >
> > Gintas
> >
> > 2018-02-26 8:10 GMT+01:00 Jan Matèrne (jhm) <[hidden email]>:
> >
> > > I recognize that the contributor [1] page is not listing Gintas.
> > >
> > > @Gintas: Could you add yourself to the source file [2] in the SVN
> > repo
> > > for the website [3], run the build and commit it back, please?
> > >
> > >
> > >
> > > Jan
> > >
> > >
> > >
> > >
> > >
> > > [1] http://ant.apache.org/contributors.html
> > >
> > > [2]
> > >
> > https://svn.apache.org/repos/asf/ant/site/ant/sources/contributors.xml
> > >
> > >     //section[name="Committers"]/subsection[name="Active Committers"]
> > >
> > > [3] https://svn.apache.org/repos/asf/ant/site/
> > >
> > >
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: committer += gintas

Stefan Bodewig
In reply to this post by Jan Matèrne (jhm)
On 2018-02-28, Jan Matèrne (jhm) wrote:

> - build, inactive repo, last change 2007, not used any more (I think)

I don't even recall what it was :-)

> If we want to migrate the site repo, we should also think about
> handling the sandbox.

I think we just never migrated it because it simply wasn't used. Using a
single git repository for several unrelated experiments doesn't sound
very git-like.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Future of SVN repos

Jan Matèrne (jhm)
> > If we want to migrate the site repo, we should also think about
> > handling the sandbox.
>
> I think we just never migrated it because it simply wasn't used. Using
> a single git repository for several unrelated experiments doesn't sound
> very git-like.

Yep.
We could migrate site to git and then close all svn repos (make them read-only).
If required someone could create a local git repo for new "sandbox experiments". Shareable via github and later moving to ASF infrastructure if it changes to be more than an experiment.

What do you think?


Jan


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Future of SVN repos

Matt Sicker
Creating new git repos on apache is self-serve, so it's just as easy as
GitHub really (though you need to be a PMC member I think).

On 28 February 2018 at 12:48, Jan Matèrne (jhm) <[hidden email]> wrote:

> > > If we want to migrate the site repo, we should also think about
> > > handling the sandbox.
> >
> > I think we just never migrated it because it simply wasn't used. Using
> > a single git repository for several unrelated experiments doesn't sound
> > very git-like.
>
> Yep.
> We could migrate site to git and then close all svn repos (make them
> read-only).
> If required someone could create a local git repo for new "sandbox
> experiments". Shareable via github and later moving to ASF infrastructure
> if it changes to be more than an experiment.
>
> What do you think?
>
>
> Jan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

AW: Future of SVN repos

Jan Matèrne (jhm)
Thanks for the reminder, Matt. So we could stay on ASF infrastructure.
https://selfserve.apache.org/ 
but for git repos https://gitbox.apache.org/

Both forms require PMC-name, repo-name, repo-description, commit-notification-list and github-notification list.
But while (for me) the selfserve-form seems to be fully functional, the gitbox-form had no entries for the PMC listbox.


Jan

> -----Ursprüngliche Nachricht-----
> Von: Matt Sicker [mailto:[hidden email]]
> Gesendet: Mittwoch, 28. Februar 2018 19:50
> An: Ant Developers List
> Betreff: Re: Future of SVN repos
>
> Creating new git repos on apache is self-serve, so it's just as easy as
> GitHub really (though you need to be a PMC member I think).
>
> On 28 February 2018 at 12:48, Jan Matèrne (jhm) <[hidden email]>
> wrote:
>
> > > > If we want to migrate the site repo, we should also think about
> > > > handling the sandbox.
> > >
> > > I think we just never migrated it because it simply wasn't used.
> > > Using a single git repository for several unrelated experiments
> > > doesn't sound very git-like.
> >
> > Yep.
> > We could migrate site to git and then close all svn repos (make them
> > read-only).
> > If required someone could create a local git repo for new "sandbox
> > experiments". Shareable via github and later moving to ASF
> > infrastructure if it changes to be more than an experiment.
> >
> > What do you think?
> >
> >
> > Jan
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email] For additional
> > commands, e-mail: [hidden email]
> >
> >
>
>
> --
> Matt Sicker <[hidden email]>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Future of SVN repos

Matt Sicker
Oh yeah, it looks like gitbox isn't self serve yet. :(

On 28 February 2018 at 13:35, Jan Matèrne (jhm) <[hidden email]> wrote:

> Thanks for the reminder, Matt. So we could stay on ASF infrastructure.
> https://selfserve.apache.org/
> but for git repos https://gitbox.apache.org/
>
> Both forms require PMC-name, repo-name, repo-description,
> commit-notification-list and github-notification list.
> But while (for me) the selfserve-form seems to be fully functional, the
> gitbox-form had no entries for the PMC listbox.
>
>
> Jan
>
> > -----Ursprüngliche Nachricht-----
> > Von: Matt Sicker [mailto:[hidden email]]
> > Gesendet: Mittwoch, 28. Februar 2018 19:50
> > An: Ant Developers List
> > Betreff: Re: Future of SVN repos
> >
> > Creating new git repos on apache is self-serve, so it's just as easy as
> > GitHub really (though you need to be a PMC member I think).
> >
> > On 28 February 2018 at 12:48, Jan Matèrne (jhm) <[hidden email]>
> > wrote:
> >
> > > > > If we want to migrate the site repo, we should also think about
> > > > > handling the sandbox.
> > > >
> > > > I think we just never migrated it because it simply wasn't used.
> > > > Using a single git repository for several unrelated experiments
> > > > doesn't sound very git-like.
> > >
> > > Yep.
> > > We could migrate site to git and then close all svn repos (make them
> > > read-only).
> > > If required someone could create a local git repo for new "sandbox
> > > experiments". Shareable via github and later moving to ASF
> > > infrastructure if it changes to be more than an experiment.
> > >
> > > What do you think?
> > >
> > >
> > > Jan
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email] For additional
> > > commands, e-mail: [hidden email]
> > >
> > >
> >
> >
> > --
> > Matt Sicker <[hidden email]>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Matt Sicker <[hidden email]>