Re: [Snowdrift-dev] What are the folders to purge to fix or prevent build issues?

2016-05-09 Thread Victor Grousset
On 08/05/2016 21:45, Bryan Richter wrote:
> On Sat, May 07, 2016 at 02:15:22PM +0200, Victor/tuxayo wrote:
>> What about adding this as a "Manual rebuild" sub section? Just after
>> "Updating static files":
> There's a "manual rebuild" section right *before*
> updating-static-files. :) You could add some content to that section,
> however (and maybe that's what you meant).

Updating-static-files is a subsection of manual rebuild. That why I
wanted to put it after. But if it makes more sense before, no problem.

Right I'll try to write something (until I manage to fix my RAM
stability issues...)

Victor Grousset
Dev mailing list

Re: [Snowdrift-dev] taiga: can't edit or comment my own issue

2016-05-03 Thread Victor Grousset/tuxayo
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:

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

Victor Grousset/tuxayo
Dev mailing list

Re: [Snowdrift-dev] taiga: can't edit or comment my own issue

2016-05-02 Thread Victor Grousset/tuxayo
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.


Victor Grousset/tuxayo
Dev mailing list