Considering to handover "Snooze Tabs" to community?

(Albert S) #1

After made it quite clear that this will not being worked on anymore, someone asked in the Addon’s comment section if it could be opened up to the community:

Posting the request here for discussion (as the sub-board has been archived).

(Blake Winton) #2

Seems reasonable, if someone can be found whose trustworthy enough to take it over… Having said that, I don’t remember anyone offering to maintain it, and no-one has been particularly active in the repo, so the tough part might be finding the right community member to maintain it.

1 Like
(lmorchard) #3

I guess the question is what do you mean by “hand over to community”?

The project is all there on Github. If someone from the community wants to pick it up, I don’t think there’s anything stopping that. Snooze Tabs in particular was built in a way that it doesn’t need any special access or permissions from Mozilla, so it’s really just a normal web extension.

The folks who were working on it (including Blake and I and others) have moved onto other things. So, we won’t have time to lead or organize a community effort. There’s an open opportunity for someone who feels strongly about the project.

As for the specific “Snooze Tabs” add-on released on - I suppose we could add folks from the community as owners to hand it off. But, I’d say that recent examples of that sort of thing blowing up into a big problem at places like NPM leaves us very reticent to turn over the keys unless someone steps up in a reliably trustworthy way.

Easiest path forward for a community effort might be to take the source and run with it under a different name. I think anyone’s welcome to do that today.

1 Like
(lmorchard) #4

Also to respond to that review on AMO:

This is used by thousands of people and has numerous flaws. If the original developers cannot support this any more it would be ideal to open it up to the community to find some other owner to support it.

For what it’s worth, Snooze Tabs was a Test Pilot experiment. Test Pilot experiments were always intended to have limited life spans and not to be polished products. They were meant to explore whether an idea was worth pursuing more seriously in Firefox itself or as long-term Mozilla products. Some experiments, even with vocal groups of users, end up not making the cut for a broader commitment with the resources we have.