|Open||Nehajha||T175768 Improvements for the Toolforge 'webservice' command|
|Resolved||Sowjanyavemuri||T176624 Outreachy - webservice microtask for Sowjanyavemuri|
|Resolved||Sowjanyavemuri||T177439 Document Tool naming contraints|
[A comment from an outsider:]
Am I right that the first bullet point is describing the current situation?
While the second and third bullet point is what you plan to work on?
- you could assign T176681 to yourself (via Add Action... → Assign / Claim in the dropdown menu) if you plan to work on that. No need to duplicate it in this task?
- make this task only about your third bullet point by editing the summary and description (by clicking ), as tasks should only cover one problem. :)
(In general, passive constructions like "is edited" can make it hard to understand if this is about the current situation described, or if it is about what needs to be done. I'd respectfully recommend to use verbs and use them in imperative mood like in commit messages, for clarity.)
Thanks for working on this!
toolsadmin has been updated to prevent invalid names, but having a note about the required naming scheme still seems like a good idea. The description now given when the name is invalid is Must start with a-z, end with a-z or 0-9, be 1-32 characters long, and can only contain lowercase a-z, 0-9, and - characters..