-
SamWhited
We already have a Trello for boards, FYI, please do not use GitHub boards. I don't really care between the two, but let's not duplicate info and everyone was already using Trello.
-
SamWhited
I have closed the GitHub boards.
-
SamWhited
Feel free to rearrange or rename columns in the trello board if you need to. If you can't, let me know and I'll fix permissions (but I think everyone can)
-
jonasw
I don’t like trello.
-
SamWhited
Me neither.
-
jonasw
any good reason not to move to github "projects"?
-
jonasw
they’re nicely integrated.
-
SamWhited
Everyone was already using Trello
-
jonasw
there’s no tight coupling between the boards, is there?
-
SamWhited
If the council has a thing on Trello, they can move it directly to the editor board. Let's not try to change our entire process just because I don't love something.
-
SamWhited
It works and is "good enough".
-
jonasw
right, maybe I don’t know trello well enough
-
SamWhited
s/I/we/
-
jonasw
what I liked about the github things is that you can see right on the PR what the status in council etc. is
-
Guus
(github has a Trello-like feature?)
-
jonasw
Guus, yeah, they added that a few months ago I think
-
SamWhited
Guus: I think they call it "Projects", it's fairly recent.
-
jonasw
I used it to track PRs through council
-
SamWhited
I assume Trello has a GitHub integration we could enable, but I haven't tried it; it was never really a problem.
-
SamWhited
I just don't want info ending up in two places with council looking at our Trello and half the stuff being on GitHub.
-
jonasw
I put the stuff on council trello whenever needed.
-
jonasw
SamWhited, what do you suggest as a means of communication so that work I do on the xeps repo (e.g. with respect to tooling) is seen by all active editors?
-
jonasw
I tried PRs on the xeps repository which apparently didn’t really help.
-
jonasw
I can ping the editors list, do you think that’d be more useful?
-
jonasw
also it’d have been nice to get some notice before you simply close the boards -- they are referenced in the current readme
-
jonasw
and I currently don’t have the time to re-work the readme
-
jonasw
also it is a bit demotivating to get my work (thought put into a process I can work efficiently with, given that there was only sparse documentation, the timezone issue noone of us can do something about and the huge backlog) reverted without a word of discussion.
-
SamWhited
jonasw: the email list would be good for communication
-
jonasw
right, let’s try that
-
SamWhited
Sorry if it's demotivating, but please don't just duplicate work that's already been done.
-
jonasw
SamWhited, I understand.
-
SamWhited
Reworked the readme: https://github.com/xsf/xeps/pull/519
-
SamWhited
If we want to change in the future that's fine, but for now let's not make the editor process require any more steps than it already does.
-
SamWhited
And let's discuss before changing the process.
-
jonasw
SamWhited, okay, fair
-
jonasw
I’m composing an email with an overview of what I did in the last month besides working on XEP updates.
-
jonasw
thanks for the fix to the readme
-
SamWhited
Sure thing; thanks for all the work you've been doing?
-
SamWhited
!, even.
-
jonasw
email sent, have fun reading it :)