Transfer Featherpad

store-requests
4

Hello, first of all, apologies for the ignorance. As the discussion is currently scattered throughout multiple places(downstream snap project issue report, upstream project issue report, Snapcraft Forum snap ownership transfer post, and the Snap Store private backstage messages), I would like to consolidate them into this Snapcraft Forum thread as it is the proper place for the matter to be discussed in the first place. I’ll also forward the same necessary portions of responses to the upstream issue report with full-quoted context as not everyone has a Snapcraft Forum account.

I, unfortunately, and regrettably, missed the communication e-mail sent by the Snap Store staff regarding the namespace transfer request assumed to be initiated by you on 5/10/2023:

Screenshot of the staff store communication
Screenshot of the staff store communication1774×697 72.8 KB

…and was wondering why there’s an unknown personnel request for the snap ownership transfer with the “ASAP” in their very first direct communication:

Screenshot of the downstream snap issue tracker snap ownership transfer request
Screenshot of the downstream snap issue tracker snap ownership transfer request1255×598 60.3 KB

Source: Transfer Snap To Me · Issue #11 · brlin-tw/featherpad-snap

Although I’m thrilled to have someone willing to devote their precious resources to address the burden of the Featherpad snap’s maintenance, I also, have the responsibility to ensure that the snap doesn’t fall into the wrong hands(I already have a bad reputation for “snap maintenance negligence”, I wouldn’t want to gain another one which is “snap ownership transfer negligence”, right?). As a result, I would like to request to temporarily suspend this ownership transfer process and focus on addressing the problems that cause the necessity for the snap ownership transfer in the first place.

To steer the matter in the right direction, I have implemented and devised a plan moving forward:

  • I have set the snap’s visibility to “unlisted,” which means it will no longer appear in search results or store listings. However, users can still install it by directly referencing the snap’s name. This action is intended to minimize the impact of the unmaintained version of the snap. The visibility setting will be restored once the maintenance status improves.
  • I hereby invite @SamAlex to directly contribute to the downstream snap project (https://github.com/brlin-tw/featherpad-snap) by following the regular GitHub development workflow of fork, pull request, review, and merge. To ensure quality assurance I would like to require the following criteria to be cleared before granting direct write access to the Git repository:
    • All necessary snap build recipe changes required to build the snap to the latest version of the upstream project must be merged into the repository. If possible, changes should be logically separated into individual commits or pull requests. In cases where logical separation is not feasible, a comprehensive enumeration of changes should be provided in the commit descriptions.
    • The snap should be buildable via the snapcraft remote-build command, at least for the AMD64 architecture.
    • A one-time maintenance notice regarding the change of project contributors must be implemented. For further details, please refer to this link. Additionally, at least 75% of the current weekly active installs should be upgraded to the revision that contains the notice.
  • Once I am fully convinced that the snap is being well taken care of, I will add @SamAlex as a store contributor to the snap. This will grant equivalent access to the store backstage, enabling the management of channel releases and other relevant tasks.

If you have any questions or concerns regarding the progress we are making, please do not hesitate to ask. I wholeheartedly welcome you aboard!

Cheers :clinking_glasses: ,
林博仁(Buo-ren, Lin)

1 Like