> On 20 Sep 2016, at 19:34, Stefan van der Walt wrote:
>
>> On Fri, Sep 16, 2016, at 01:35, François Boulogne wrote:
>> I think we need to determine how many boards we want (what github call
>> project, I don't like this word... anyway).
>> A big one with the progress or
I'm just discovering this new feature.
It looks like we need to organize ourself because sorting issues in the
column of a project is like duplicating the labels "status" we have on
issues.
I didn't find a way to automatically import issues, but we can search a
label and drag the "cards".
I
Yes, crazy timing! =D
On 15 September 2016 at 9:08:59 AM, Stefan van der Walt (
stef...@berkeley.edu) wrote:
On Mon, Aug 29, 2016, at 13:17, Stefan van der Walt wrote:
> I have some ideas around (1) that need fleshing out, but in the mean
> time I was looking at http://zube.io to address part
On Mon, Sep 5, 2016 at 10:42 PM, Stefan van der Walt
wrote:
> On Sun, Sep 4, 2016, at 01:32, Egor Panfilov wrote:
>
> You mean RFCs like PEPs?
>
>
> Exactly. I think, this format would help to accumulate our opinions on
> different matters (e.g. how to we treat and depend
Hi Johannes
On Tue, Aug 30, 2016, at 12:58, Johannes Schönberger wrote:
> I agree that Github does not provide a good overview of active/passive
> issues. I am overwhelmed by the amount of issues and, usually, after a
> week of scikit-image "abstinence" :-), I have to start from scratch to
> find
Hi Stéfan,
thanks for continuing the discussion on this important subject. I would
reformulate your two points as 1) social aspects/community management and
2) technical tools and processes.
In my opinion, we need a little bit of both. Dashboards can be useful if
they save time and provide
Hi, everyone
As Juan mentioned recently, it's becoming harder to keep track of the
motion of the project as a whole. Sometimes, tickets lounge unattended
for an unacceptable long time.
I can think of two main routes for improving the situation:
1) Improve our team structure, so that