Documentation -> flowlog.net -> Issues -> Feature Request Guidelines

A Proper Title

The goals of the feature request title are similar to that of a bug report title. We want to succinctly describe the feature in the title so that people can find features that have already been requested and/or understand the feature request without having to view the feature request's page and so that web or flowlog.net searches actually turn up useful results for people.

A Useful Description

Please try to include any information that would make your desired feature understandable to a flowlog developer, preferably without them having to ask any questions. What does it do? what problems does it solve? How do you envision it would best be made visible/available to the end user? Why do you believe it's worth the trouble to implement the feature? why do you think it fits within the design scope of flowlog, etc. All these suggestions will not apply to every feature, but should be included when you know that information is applicable to your feature request. If you're not sure if some of these apply to your feature request that's ok, devs can follow up. We just want our original FRs to be as actionable as possible.

Thanks to members!

flowlog members are actively responsible for how useful and easy to use their own resources are, by how they use them themselves. Thanks for helping make flowlog.net better for everyone!