Changes

# The reporter also posts to the [lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] list with a link to the bug report and asks if anyone knows how to contact the maintainer.

# The reporter also posts to the [lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] list with a link to the bug report and asks if anyone knows how to contact the maintainer.

# After 7 more days (now 2 weeks total), the reporter posts a formal request to the sugar-devel list with the bug link, indicating all reasonable efforts to contact the maintainer have failed and that they wish to take over the package.

# After 7 more days (now 2 weeks total), the reporter posts a formal request to the sugar-devel list with the bug link, indicating all reasonable efforts to contact the maintainer have failed and that they wish to take over the package.

# If at least one [[SLOBs]] member approves the takeover, and no one objects within 3 days, the reporter may take over the package.

# If at least one [[Activity_Team/Contacts|Activity Team Coordinator]] or [[SLOBs]] member approves the takeover, and no one objects within 2 days, the reporter may take over the package.

# Once approval has been given, the reporter can request the [[Infrastructure Team]] to change ownership of the Activity in [[Service/git|git]], [[Service/bugs|trac]] and [[Service/activities|ASLO]]. In addition to this, the new owner must also reassign all open bugs for this package to themselves.

# Once approval has been given, the reporter can request the [[Infrastructure Team]] to change ownership of the Activity in [[Service/git|git]], [[Service/bugs|trac]] and [[Service/activities|ASLO]]. In addition to this, the new owner must also reassign all open bugs for this package to themselves.

</onlyinclude>

</onlyinclude>

== Notes for Mass Orphaning ==

== Notes for Mass Orphaning ==

* It is common for a Sugar Labs contributor to maintain multiple activities, and the situation may arise where multiple activities with a single maintainer need to be orphaned. Given that, it would be quite impractical to create a ticket for each activity. In the case where a mass orphaning is likely, the above should still be followed choosing a single package owned by the potential non-responsive developer. However, the formal request to the Sugar development mailing list should include all other bug reports open on all neglected activities from the same maintainer, indicating that the maintainer is indeed non-responsive. The [[SLOBs]] can then step in and orphan the other activities if necessary.

* It is common for a Sugar Labs contributor to maintain multiple activities, and the situation may arise where multiple activities with a single maintainer need to be orphaned. Given that, it would be quite impractical to create a ticket for each activity. In the case where a mass orphaning is likely, the above should still be followed choosing a single package owned by the potential non-responsive developer. However, the formal request to the Sugar development mailing list should include all other bug reports open on all neglected activities from the same maintainer, indicating that the maintainer is indeed non-responsive. The [[Activity_Team/Contacts|Activity Team Coordinators]] can then step in and orphan the other activities if necessary.

== Notes for maintainers ==

== Notes for maintainers ==

Steps:  

Steps:  

* Write email to the sugar-devel list with the non-responsive maintainer CC'ed on the post. Explain why you think the fast track process is needed.  

* Write email to the sugar-devel list with the non-responsive maintainer CC'ed on the post. Explain why you think the fast track process is needed. (Make sure and note any communication attempt done already)

(Make sure and note any communication attempt done already)

* Open a ticket with the maintainers' account CC'ed.

* Open a ticket with the maintainers' account CC'ed.

* The next [[SLOBs]] meeting will discuss the case and reach a decision.

* The next [[Activity_Team/Meetings|Activity Team meeting]] will discuss the case and reach a decision.

[[Category:Policy]]

[[Category:Policy]]

[[Category:Activities]]

[[Category:Activities]]