Replying to Avatar wuwei

Problem: nostrocket is not currently applicable to more than a few people

The nostrocket implementation is currently lacking most of the features that are described in the unprotocol.

This means most people are not really able to use nostrocket for very much. It's only really applicable to a few people at this stage because it takes a lot of time and effort to understand what it is and even more to get involved.

Solution: start adding problems nested under this one when it relates to the implementation and UX of Spaceman, Engine, the Relay, etc.

Whenever logging a problem, think: does solving this problem make bring Nostrocket closer to another participant getting involved?
Avatar
gsovereignty 2y ago

Problem: can't modify products

I want to be able to modify the description of a nostrocket product that I have created but this is currently not possible.

Solution: allow the product creator or a maintainer (of the parent rocket) to update product data (price, and the event ID of the product description)

Reply to this note

Please Login to reply.

Discussion

Avatar
gsovereignty 2y ago

Problem: sub-rockets can't have their own maintainers

The maintainer tree is currently global, and so there are only Nostrocket maintainers.

Sometimes it's going to be neccessary to have a maintainer tree that is specific to a particular rocket, e.g. for updating products.

Avatar
gsovereignty 2y ago

I'm claiming [Problem: sub-rockets can't have their own maintainers] on the nostrocket problem tracker so that I can work on it and other people don't duplicate my efforts.

Avatar
gsovereignty 2y ago

I'm closing [Problem: sub-rockets can't have their own maintainers] on the nostrocket problem tracker, it's been resolved or become obsolete.