[Process] Proposal to revise unmaintained charms workflow

[José Antonio Rey]

+1 here. I would expect it to be dropped as soon as it's requested/filed.
Plus, all the code would not be lost, since it's moved to
~unmaintained-charms.

--
José Antonio Rey

On Fri, Sep 4, 2015, 12:43 Marco Ceppi <marco.ceppi at canonical.com> wrote:

> Though you didn't ask, it's a +1 from me. I think the current process is
> more gauged at weeding out charms that are abandoned by authors and doesn't
> have a declaration for how to handle the use case where an author
> explicitly wishes to drop maintainership.
>
>
> Marco
>
> On Fri, Sep 4, 2015 at 1:40 PM Charles Butler <
> charles.butler at canonical.com> wrote:
>
>> Greetings,
>>
>> We've recently encountered a scenario where our verbiage in the
>> unmaintained charm process is a tad confusing and limiting given the
>> scenario that a charm author requests to no longer maintain their charm.
>>
>> For reference, the document in question is located here:
>> https://jujucharms.com/docs/stable/charm-unmaintained-process
>>
>> Given the scenario that a charm author wishes to maintain their charm and
>> informs ~charmers they will no longer be developing, patching, or updating
>> - essentially abandoned the charm - the verbiage states:
>>
>>
>>
>>    1.
>>
>>    File a bug against charm saying “Maintainer needed”
>>    2.
>>
>>    Is charm broken?
>>    1.
>>
>>       Follow “Workflow for identifying and triaging unmaintained charms”
>>       process
>>
>>
>> This particular process includes a 30 day wait period to take *any*
>> action on the charm. What we would like to propose is:
>>
>> A bug be filed for "Maintainer Needed", the charm be moved to
>> ~unmaintained-charms, and a call to arms be issued to the list for a new
>> maintainer. Thus not leaving a potentially broken charm in the charm-store
>> for an extended time-wait scenario, allowing other potential consumers to
>> encounter the unmaintained, and potentially broken charm.
>>
>> If someone steps into the role of maintainership, it's a simple process
>> to put the charm back in the store under the new maintainer.
>>
>> If you have any dispute with this potential change, please respond to
>> this thread. No verbal dispute will constitute acceptance, and we will
>> amend during the Charmer Summit starting Sept 17th.
>>
>> Thanks
>>
>> Charles Butler <charles.butler at canonical.com> - Juju Charmer
>> Come see the future of datacenter orchestration: http://jujucharms.com
>> --
>> Juju mailing list
>> Juju at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20150904/58b81dc2/attachment.html>