Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On 03/05/2016 17:34, Stephen Michel wrote: > The taiga project doesn't allow external users to create issues, so you > send them feedback and they create issues themselves. Here's one for the > feature we're talking about: https://tree.taiga.io/project/taiga/issue/2132 Thanks, feedback sent. -- Victor/tuxayo ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On Tue, May 3, 2016 at 9:25 AM, Victor Grousset/tuxayo wrote: On 02/05/2016 20:16, Bryan Richter wrote: On Sun, May 01, 2016 at 12:05:16PM +0200, Victor Grousset/tuxayo wrote: For command line email readers or are there others reasons? It's usually a lot more usable in a lot more contexts. For instance, your message was completely eaten on the archives: https://lists.snowdrift.coop/pipermail/dev/2016-April/000319.html Indeed, that pretty bad :-( On 02/05/2016 23:07, Stephen Michel wrote: I have already submitted a feature request for issue creators to be able to comment on and edit their own issues. However, more people doesn't hurt! I can't find your feature request among the issues at https://tree.taiga.io/project/taiga/issues The taiga project doesn't allow external users to create issues, so you send them feedback and they create issues themselves. Here's one for the feature we're talking about: https://tree.taiga.io/project/taiga/issue/2132 ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On 02/05/2016 20:16, Bryan Richter wrote: > On Sun, May 01, 2016 at 12:05:16PM +0200, Victor Grousset/tuxayo wrote: >> For command line email readers or are there others reasons? > > It's usually a lot more usable in a lot more contexts. For instance, > your message was completely eaten on the archives: > > https://lists.snowdrift.coop/pipermail/dev/2016-April/000319.html Indeed, that pretty bad :-( On 02/05/2016 23:07, Stephen Michel wrote: > I have already submitted a feature request for issue creators to be able > to comment on and edit their own issues. However, more people doesn't > hurt! I can't find your feature request among the issues at https://tree.taiga.io/project/taiga/issues -- Victor Grousset/tuxayo ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On Mon, May 2, 2016 at 2:19 PM, Bryan Richter wrote: On Mon, May 02, 2016 at 12:00:59PM +0200, Victor Grousset/tuxayo wrote: On 01/05/2016 14:25, Stephen Michel wrote: > Unfortunately, Taiga does not have a separate permission for > editing your own posts or commenting on posts -- they are both > under the 'edit' permission. So in order for me to allow you to > comment and edit by default, I'd have to allow the public to edit > any issue. I can add you to the project so you can comment/edit. > >> Should I have used Taiga in the first place to ask about updating >> the links in the repository? > > I'll have some documentation out about how we use our tools soon, > but the short answer is that Taiga issues is a good place for > everything The restriction on commenting could be a barrier to new contributors wanting to report bugs and make suggestions. Will there be an alternative workflow for new contributors? The mailing list is a fallback but it's not very convenient as a bug tracker. (GitLab issues?) This is actually a pretty big deal. We haven't really nailed down how to have volunteers submit issues and so forth. Maybe we should use Gitlab issues for now? Since they feed into Taiga, we (the team) can still use Taiga to track upcoming work, while other people can still contribute. We should also submit feature requests to Taiga. Victor, would you be willing to do that? I have already submitted a feature request for issue creators to be able to comment on and edit their own issues. However, more people doesn't hurt! You can also go through their issues backlog [1] and vote on issues that you think are important. [1]: https://tree.taiga.io/project/taiga/issues ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On Mon, May 02, 2016 at 12:00:59PM +0200, Victor Grousset/tuxayo wrote: > On 01/05/2016 14:25, Stephen Michel wrote: > > Unfortunately, Taiga does not have a separate permission for > > editing your own posts or commenting on posts -- they are both > > under the 'edit' permission. So in order for me to allow you to > > comment and edit by default, I'd have to allow the public to edit > > any issue. I can add you to the project so you can comment/edit. > > > >> Should I have used Taiga in the first place to ask about updating > >> the links in the repository? > > > > I'll have some documentation out about how we use our tools soon, > > but the short answer is that Taiga issues is a good place for > > everything > > The restriction on commenting could be a barrier to new contributors > wanting to report bugs and make suggestions. Will there be an > alternative workflow for new contributors? The mailing list is a > fallback but it's not very convenient as a bug tracker. (GitLab > issues?) This is actually a pretty big deal. We haven't really nailed down how to have volunteers submit issues and so forth. Maybe we should use Gitlab issues for now? Since they feed into Taiga, we (the team) can still use Taiga to track upcoming work, while other people can still contribute. We should also submit feature requests to Taiga. Victor, would you be willing to do that? signature.asc Description: Digital signature ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On Sun, May 01, 2016 at 12:05:16PM +0200, Victor Grousset/tuxayo wrote: > On 30/04/2016 16:07, Peter Harpending wrote: > > Please do not send HTML mail to a mailing list. > > Thanks, noted I'll try to remember. > > > (Or, ideally, at all). > > For command line email readers or are there others reasons? It's usually a lot more usable in a lot more contexts. For instance, your message was completely eaten on the archives: https://lists.snowdrift.coop/pipermail/dev/2016-April/000319.html signature.asc Description: Digital signature ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On Mon, May 2, 2016 at 10:02 AM, Peter Harpending wrote: On Mon, May 02, 2016 at 08:40:45AM -0400, Stephen Michel wrote: >On 01/05/2016 23:07, Peter Harpending wrote: >> Mostly for terminal-based email readers, I think > >Thanks, I'll try to be careful about the email format now. I'm pretty sure some email clients can send both html and text, and the client on the other side can choose which to display. I would argue that it's much easier for most people to just not send HTML email than to explain how to set this up. Also, it occurs to me that the archives on mailman won't render HTML mail correctly, which is yet another reason to use plain-text email. Some clients do it automatically, I believe. (Like mine, I think). italics ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On Mon, May 02, 2016 at 08:40:45AM -0400, Stephen Michel wrote: > >On 01/05/2016 23:07, Peter Harpending wrote: > >> Mostly for terminal-based email readers, I think > > > >Thanks, I'll try to be careful about the email format now. > > I'm pretty sure some email clients can send both html and text, and the client > on the other side can choose which to display. I would argue that it's much easier for most people to just not send HTML email than to explain how to set this up. Also, it occurs to me that the archives on mailman won't render HTML mail correctly, which is yet another reason to use plain-text email. Peter Harpending signature.asc Description: Digital signature ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On May 2, 2016 6:00:59 AM EDT, Victor Grousset/tuxayo wrote: >On 01/05/2016 14:25, Stephen Michel wrote: >> Unfortunately, Taiga does not have a separate permission for editing >your own posts or commenting on posts -- they are both under the 'edit' >permission. So in order for me to allow you to comment and edit by >default, I'd have to allow the public to edit any issue. I can add you >to the project so you can comment/edit. >> >>> Should I have used Taiga in the first place to ask about updating >the >>> links in the repository? >> >> I'll have some documentation out about how we use our tools soon, but >the short answer is that Taiga issues is a good place for everything > >The restriction on commenting could be a barrier to new contributors >wanting to report bugs and make suggestions. Will there be an >alternative workflow for new contributors? >The mailing list is a fallback but it's not very convenient as a bug >tracker. (GitLab issues?) If you create or comment on a gitlab or github issue, it should automatically import into Taiga. >On 01/05/2016 23:07, Peter Harpending wrote: >> Mostly for terminal-based email readers, I think > >Thanks, I'll try to be careful about the email format now. I'm pretty sure some email clients can send both html and text, and the client on the other side can choose which to display. -- Email Policy: http://stephenmichel.me/email ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On 01/05/2016 14:25, Stephen Michel wrote: > Unfortunately, Taiga does not have a separate permission for editing your own > posts or commenting on posts -- they are both under the 'edit' permission. So > in order for me to allow you to comment and edit by default, I'd have to > allow the public to edit any issue. I can add you to the project so you can > comment/edit. > >> Should I have used Taiga in the first place to ask about updating the >> links in the repository? > > I'll have some documentation out about how we use our tools soon, but the > short answer is that Taiga issues is a good place for everything The restriction on commenting could be a barrier to new contributors wanting to report bugs and make suggestions. Will there be an alternative workflow for new contributors? The mailing list is a fallback but it's not very convenient as a bug tracker. (GitLab issues?) On 01/05/2016 23:07, Peter Harpending wrote: > Mostly for terminal-based email readers, I think Thanks, I'll try to be careful about the email format now. Cheers, -- Victor Grousset/tuxayo ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On Sun, May 01, 2016 at 12:05:16PM +0200, Victor Grousset/tuxayo wrote: > On 30/04/2016 16:07, Peter Harpending wrote: > > Please do not send HTML mail to a mailing list. > > Thanks, noted I'll try to remember. > > > (Or, ideally, at all). > > For command line email readers or are there others reasons? > Mostly for terminal-based email readers, I think signature.asc Description: Digital signature ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On April 30, 2016 8:24:07 AM EDT, Victor Grousset/tuxayo wrote: >Hi, > >I just opened >https://tree.taiga.io/project/snowdrift/issue/304 > >However I wanted to updated the title and improve the formatting of the >content but I can't. >Nor comment to add more details and discuss the issue. > >Is this to be expected? Unfortunately, Taiga does not have a separate permission for editing your own posts or commenting on posts -- they are both under the 'edit' permission. So in order for me to allow you to comment and edit by default, I'd have to allow the public to edit any issue. I can add you to the project so you can comment/edit. >Should I have used Taiga in the first place to ask about updating the >links in the repository? I'll have some documentation out about how we use our tools soon, but the short answer is that Taiga issues is a good place for everything (except governance issues of the snowdrift.coop team, and those are the kind of thing where if you're unsure whether they're relevant to you, they are probably irrelevant). -- Email Policy: http://stephenmichel.me/email ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On 30/04/2016 16:07, Peter Harpending wrote: > Please do not send HTML mail to a mailing list. Thanks, noted I'll try to remember. (Or, ideally, at all). For command line email readers or are there others reasons? -- Victor Grousset/tuxayo ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] taiga: can't edit or comment my own issue
On Sat, Apr 30, 2016 at 02:24:07PM +0200, Victor Grousset/tuxayo wrote: > > > > > > > Hi, > > I just opened > href="https://tree.taiga.io/project/snowdrift/issue/304";>https://tree.taiga.io/project/snowdrift/issue/304 > > However I wanted to updated the title and improve the formatting of > the content but I can't. > Nor comment to add more details and discuss the issue. > > Is this to be expected? > Should I have used Taiga in the first place to ask about updating > the links in the repository? > > > Cheers, > -- > Victor Grousset/tuxayo > > Please do not send HTML mail to a mailing list. (Or, ideally, at all). Peter Harpending signature.asc Description: Digital signature ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
