[Product-Developers] How attached to POI issue trackers are we?
T. Kim Nguyen
nguyen at uwosh.edu
Fri Feb 10 05:25:47 UTC 2012
I'd like to hear your ideas on sunsetting Poi. Might as well get em out there!
At the very least something that generates semi-structured text files out of the contents of a Poi would help. And I am so overcommitted now already it's just not funny anymore...
Kim
On Feb 9, 2012, at 11:21 PM, Ross Patterson wrote:
> "T. Kim Nguyen" <nguyen at uwosh.edu> writes:
>
>> I'm sure there would be wide support for allowing existing Poi on
>> plone.org to continue being used, and not allowing new Poi to be
>> created on plone.org.
>>
>> If Poi eventually are to be shut off entirely on plone.org then it
>> would be good to have a moderately decent export / import mechanism; I
>> have no idea if there is such a thing today, however.
>
> Export/import is a great idea and I think you should do it! :-)
>
> But seriously, I'm just addressing the, IMO, erroneous conflation of a
> community making smart decisions of where to put its energy with
> coercion.
>
> I have more to say on the possibility of sunsetting Poi but since it's
> not proposed, I'll wait.
>
> Ross
>
>> On Feb 9, 2012, at 6:33 PM, Ross Patterson wrote:
>>
>>> Andreas Jung <lists at zopyx.com> writes:
>>>
>>>> Sorry guys but once again: you can not force a project to move to
>>>> Github (sources and trackers) without explicit agreement of the
>>>> package owner or current package maintainer - at least not
>>>> for active packages where let's say the issue tracker is actively
>>>> used (last activity happened within the last X months).
>>>
>>> We can and should be smart about the software we commit ourselves to
>>> maintain. Our community time, energy and ingenuity is valuable and
>>> should be focused on making a better CMS, not supporting and maintaining
>>> a very old, and passable but not terribly good issue tracker. Our
>>> users' time, energy, and experience is also very valuable and should be
>>> cared for when they report problems with or request features of the
>>> add-ons they use. It is not only appropriate, but important for all of
>>> this to be taken into account when asking the kind of questions being
>>> asked here. It is also appropriate and important to be asking these
>>> kinds of questions.
>>>
>>> Ros
>>>
>>>> Nathan Van Gheem wrote:
>>>>> I wouldn't need them exported. We could just close them to new
>>>>> submissions for a period before completely shutting em down.
>>>>>
>>>>> On Wed, Feb 8, 2012 at 9:57 PM, Jon Stahl
>>>>> <jonstahl at gmail.com
>>>>> <mailto:jonstahl at gmail.com>> wrote:
>>>>>
>>>>> On Wed, Feb 8, 2012 at 4:41 PM, derek
>>>>> <auspex at pointerstop.ca
>>>>> <mailto:auspex at pointerstop.ca>> wrote:
>>>>>> On Feb 8, 3:48 pm, Nathan Van Gheem
>>>>>> <vangh... at gmail.com
>>>>> <mailto:vangh... at gmail.com>> wrote:
>>>>>>> I still use them but would rather not. If you put a deprecation
>>>>> date up,
>>>>>>> it'd help force me to more more of my packages to github and
>>>>> startup the
>>>>>>> tracker there also.
>>>>>>>
>>>>>>> +1 for github hosted. Very nice to have it coupled with the code
>>>>> repo.
>>>>>>
>>>>>> Yeah, I've happily used POI for years, but I'll even more happily
>>>>>> use github. I have no attachment to POI (though I thank the
>>>>>> authors for the use I've had).
>>>>>
>>>>> Thanks, Derek and Nathan. A follow-up, if I may... if POI trackers
>>>>> were gracefully deprecated, would you need to be able to get an
>>>>> export of tickets or are there few enough that you could deal with
>>>>> it manually?
>>>>>
>>>>> :jon _______________________________________________
>>>>> Product-Developers mailing list
>>>>> Product-Developers at lists.plone.org
>>>>> <mailto:Product-Developers at lists.plone.org>
>>>>> https://lists.plone.org/mailman/listinfo/plone-product-developers
>>>>>
>>>>>
>>>>> _______________________________________________ Product-Developers
>>>>> mailing list Product-Developers at lists.plone.org
>>>>> https://lists.plone.org/mailman/listinfo/plone-product-developers
>>>>
>>>>
>>>> --
>>>> ZOPYX Limited | zopyx group
>>>> Charlottenstr. 37/1 | The full-service network for Zope & Plone
>>>> D-72070 Tübingen | Produce & Publish
>>>> www.zopyx.com | www.produce-and-publish.com
>>>> ------------------------------------------------------------------------
>>>> E-Publishing, Python, Zope & Plone development, Consulting
>>>
>>> _______________________________________________
>>> Product-Developers mailing list
>>> Product-Developers at lists.plone.org
>>> https://lists.plone.org/mailman/listinfo/plone-product-developers
>
> _______________________________________________
> Product-Developers mailing list
> Product-Developers at lists.plone.org
> https://lists.plone.org/mailman/listinfo/plone-product-developers
More information about the Product-Developers
mailing list