Is P4A alive?
Diego Rubert
I was wondering if P4A is alive, because I see no news and nothing new
on the site... Anyone knows how is the project progress?
Regards,
Diego
Diego Rubert
something behind on uninstall, even breaking the whole site. Until now
no news...
--
Diego P. Rubert
Coordenadoria de Informática
Procuradoria da República no Estado de Mato Grosso do Sul
Ministério Público Federal
Diego Rubert escreveu:
Noe Misael Nieto Arroyo
Sean Kelley
Sean Kelley
Enzo Cesanelli
Anyway it would be really a shame to dismiss P4A since there's a lot of
great work there.
I suggest to move all the P4A repository to the collective in order to
improve the community participation to the project.
Just my 2 cents,
Enzo
Ross Patterson
> Nate Aune answered me 20 days ago but then no other sign.
>
> Anyway it would be really a shame to dismiss P4A since there's a lot
> of great work there.
>
> I suggest to move all the P4A repository to the collective in order to
> improve the community participation to the project.
support moving the P4A repo moved into the collective so long as there's
a way to preserve the history. Is that possible?
Ross
Lennart Regebro
2009/6/11 Ross Patterson <m...@rpatterson.net>:
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 64
Nate Aune
>> improve the community participation to the project.
>
> I have been thinking about this option a lot recently too. I think I'd
> support moving the P4A repo moved into the collective so long as there's
> a way to preserve the history. Is that possible?
I would be open to this if the SVN history could be preserved. The
only drawback is then we won't have the SVN repo browseable from the
same Trac instance where we track all the bugs/issues.
http://dev.plone4artists.org
But I'm sure that if p4a were in the collective, it would probably see
more contributions and activity, so I'd like to hear from other folks
if it's possible to move and preserve the svn history.
Nate
--
Nate Aune - na...@jazkarta.com
http://www.jazkarta.com
Nate Aune
My apologies if no one responded to your messages. Plone4Artists is a
volunteer-run effort, and it's expected that the community of users
will help each other. My time is limited such that I'm unable to
provide ongoing support to the Plone4Artists project. Does this mean
that the project is dead? No, but it does mean that other users of the
p4a tools will need to step in and assume ownership of the add-ons.
This means answering questions that are posed to the list, responding
to submitted bugs, and making regular releases of the add-ons.
Lennart Regebro has been tirelessly shepherding the p4acalendar tool
through several iterations of development. Thanks to his efforts, and
the efforts of other contributors, the calendar tool is being improved
on a continuous basis. We need similar champions for the audio and
video components. Anyone interested?
Nate
Andreas Jung
>
> But I'm sure that if p4a were in the collective, it would probably see
> more contributions and activity, so I'd like to hear from other folks
> if it's possible to move and preserve the svn history.
Andreas
Tom
>
>>> improve the community participation to the project.
>>>
>> I have been thinking about this option a lot recently too. I think I'd
>> support moving the P4A repo moved into the collective so long as there's
>> a way to preserve the history. Is that possible?
>>
>
-Tom
Lennart Regebro
> But I'm sure that if p4a were in the collective, it would probably see
> more contributions and activity, so I'd like to hear from other folks
> if it's possible to move and preserve the svn history.
It should be possible if we get the help from whoever manages the
plone svn. Which I'm sure we'll get.
Diego Rubert
give some help with plone addons, but only translations for now...
Long life to P4A! :-)
Nate Aune escreveu:
Ross Patterson
collective instead of it's own repository. It seems like others are now
warming to this idea as well. The biggest issue would, of course, be
preserving the version history.
Is there an option for merging the P4A repository into the collective
such that revision history is preserved? What can I do to help move any
of this forward?
Ross
Lennart Regebro <len...@jazkarta.com> writes:
> 2009/6/15 Nate Aune <na...@jazkarta.com>:
>
> > Ross Patterson <m...@rpatterson.net> writes:
> >
> > > Enzo Cesanelli <en...@noiza.com> writes:
> > >
> > >> Nate Aune answered me 20 days ago but then no other sign.
> > >>
> > >> Anyway it would be really a shame to dismiss P4A since there's a
> > >> lot of great work there.
> > >>
> > >> I suggest to move all the P4A repository to the collective in
> > >> order to improve the community participation to the project.
> > >
> > > I have been thinking about this option a lot recently too. I
> > > think I'd support moving the P4A repo moved into the collective so
> > > long as there's a way to preserve the history. Is that possible?
>>
Lennart Regebro
> Yep: http://subversion.tigris.org/faq.html#multi-merge . I'd be happy to do
> it if this is what everybody wants to do.
+1 from me.
Ross Patterson
>> Is there an option for merging the P4A repository into the collective
>> such that revision history is preserved? What can I do to help move
>> any
>> of this forward?
>
> Yep: http://subversion.tigris.org/faq.html#multi-merge . I'd be happy
> to do it if this is what everybody wants to do.
+1, but I guess that's obvious. :)
What would you need from the current P4A SVN server if anything? Just
the "svnadmin dump"?
Ross
Ross Patterson
> Go for it! Yeah, I think a 'sane' svn dump is all you need, I think
> that is what I used here: https://dev.plone.org/plone.org/ticket/1094(I vaguely remember asking jpetazzo to tweak the dump a bit to get
> things right.)
Looking quickly at svnadmin and svndumpfilter (the tools I'm familiar
with) the meaning of tweaking and massaging and how to accomplish what
is described in that ticket isn't clear for me. Know where I might get
more info?
> IOW, the dump should probably contain a top-level p4a dir that
> contains all the packages (if you care about that sort of thing ;-)
So would the idea be that
http://dev.plone4artists.org/svn/projects/p4a.image/trunk, for example,
should become https://svn.plone.org/svn/collective/p4a/p4a.image/trunk?
Thanks for the help and I'm excited that we're going to be able to do
this. I'll start the discussion on the P4A list concerning community
communication, modifying externals, shutting down write access on the
old repo.
Ross
>> _______________________________________________
>> Admins mailing list
>> Adm...@lists.plone.org
>> http://lists.plone.org/mailman/listinfo/admins
Ross Patterson
> Alex Clark <acl...@aclark.net> writes:
>
>> Go for it!
...
> Thanks for the help and I'm excited that we're going to be able to do
> this. I'll start the discussion on the P4A list concerning community
> communication, modifying externals, shutting down write access on the
> old repo.
So we have a confirmation that we can merge the P4A SVN, with full
revision history, into the collective. I'll continue hashing out the
technical details on the Plone Admins list. In the meantime, we need to
discuss what the shutdown procedure should be for the existing P4A repo
and how to communicate this to the community of P4A users. Suggestions?
Firstly, I would, suggest that we release to PyPI and/or plone.org
(alpha or development releases should be fine) anything for which there
is not a current release available. This will give most consumers of
P4A code that are on SVN checkouts an easier option that is also more
in-line with best practices and will alleviate some of the disruption of
retiring the existing repo. I will make releases of the p4a.*image
packages I have been working on. What other packages need releases?
Who will take care of those? This step can and can be done as soon as
now, so please do so if you can. :)
Then we should set and announce two shutdown dates, a first one for
shutting down write access and doing the actual merge with the
collective, then a second one for final shut down of read access. I do
think the second one is important to do relatively close to the shutdown
of write access or else the announcement will drift out of memory and
people will be more surprised when read access disappears in the distant
future. I don't have, however, any ideas as to what these two deadlines
should be. Suggestions? Also, how do we shutdown write access or
otherwise put a repo into read-only mode? Who can be responsible for
that?
There are also externals in the buildouts that will need to be adjusted
once the merge is complete. I don't think I will have time to adjust
the externals given my schedule and the rest I will be doing for this.
Is someone else willing to take the lead on that?
I'm excited to be making the P4A code base more available for use *and*
contribution. :)
Ross
Ross Patterson
> Ross Patterson <m...@rpatterson.net> writes:
>
>> Alex Clark <acl...@aclark.net> writes:
>>
>>> Go for it!
> ...
>> Thanks for the help and I'm excited that we're going to be able to do
>> this. I'll start the discussion on the P4A list concerning community
>> communication, modifying externals, shutting down write access on the
>> old repo.
Well, given the flood of responses and debates this has generated, I'm
afraid I'm going to have to be dictatorial and make a unilateral
decision. :)
Seriously though, since no one is replying, I'm going to decide that
we'll do the migration to the collective and shutdown of write access
on, or about, the 11th of July. Keep an eye on this list for the
announcement which will include the details including how to update your
checkouts.
We'll then retire the repository, including read access on, or about,
the 25th of July. No one has yet stepped up to update the buildout
externals and if no one does then we can expect them to be in a broken
state after the repository is retired.
Onward!
Ross
Lennart Regebro
> We'll then retire the repository, including read access on, or about,
> the 25th of July. No one has yet stepped up to update the buildout
> externals and if no one does then we can expect them to be in a broken
> state after the repository is retired.
I can update them, I want to reorganize the Dateable products as well,
I'll do that at the same time.
Diego Rubert
-- Diego P. Rubert Coordenadoria de Informática Procuradoria da República no Estado de Mato Grosso do Sul Ministério Público Federal
Ross Patterson
> Ross Patterson <m...@rpatterson.net> writes:
>
>> Ross Patterson <m...@rpatterson.net> writes:
>>
>>> Alex Clark <acl...@aclark.net> writes:
>>>
>>>> Go for it!
>> ...
>>> Thanks for the help and I'm excited that we're going to be able to do
>>> this. I'll start the discussion on the P4A list concerning community
>>> communication, modifying externals, shutting down write access on the
>>> old repo.
>
> Well, given the flood of responses and debates this has generated, I'm
> afraid I'm going to have to be dictatorial and make a unilateral
> decision. :)
>
> Seriously though, since no one is replying, I'm going to decide that
> we'll do the migration to the collective and shutdown of write access
> on, or about, the 11th of July. Keep an eye on this list for the
> announcement which will include the details including how to update your
> checkouts.
FYI, None of the Plone admins were available on the 11th so we'll be
doing this move on the 13th instead.
Ross
Ross Patterson
merged into the Plone collective subversion repository thanks to the
efforts of the fine Plone admins and various members of the P4A
community.
If you have any checkouts from the plone4artists.org repository you'll
need to replace them with new checkouts changing the URLs used as
follows:
http://www.plone4artists.org/svn/projects -> https://svn.plone.org/svn/collective/p4a
http://dev.plone4artists.org/svn/projects -> https://svn.plone.org/svn/collective/p4a
Currently, read-only access is still available at the old URLs but that
will be switched off on the 25th of July.
Enjoy,
Ross
Ross Patterson
> 2009/6/26 Ross Patterson <m...@rpatterson.net>:
>> We'll then retire the repository, including read access on, or about,
>> the 25th of July. No one has yet stepped up to update the buildout
>> externals and if no one does then we can expect them to be in a broken
>> state after the repository is retired.
>
> I can update them, I want to reorganize the Dateable products as well,
> I'll do that at the same time.
You may proceed. Note that I updated p4a.buildout/trunk/src externals
already to test the move.
Thanks!
Ross
david bain
SplashStart - Professional Websites. Starting Now.
http://www.splashstart.com
Ross Patterson
> Not to add to your burden, but do you have notes on this process? For
> the sake of others who may want to bring stuff from other svn repos
> into the collective.
see those archives. Here's the pipeline I used to generate the dump
file from the P4A repo:
svnadmin dump /mnt/misc/svn/repos/p4a | svndumpfilter include --drop-empty-revs /projects | svndumpfilter exclude --drop-empty-revs /projects/foo | svndumpfilter exclude --drop-empty-revs /projects/p4a.image/trunk/p4a/image/tests/samples/tpl.tif | sed -e 's/^Node\(-.*\|\)-path: projects/Node\1-path: p4a/' > p4a-to-collective.svn-dump
I'd actually love it if someone would put all this into a document
somewhere, but I'm definitely beyond my time allowance on this. Any
chance you can put it all together?
Ross