-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move Meeting Notes to ipfs/pm #130
Comments
Hi Marcin, does this mean to watch new meeting notes, I should follow the
other repo instead of here?
…On Mon, Nov 5, 2018 at 12:59 PM Marcin Rataj ***@***.***> wrote:
All other WGs moved to:
https://github.com/ipfs/pm/tree/master/meeting-notes/2018
During #127 <#127> we
decided to do the same.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#130>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADDtzSwBw1K36wkyI7WxIE60u09Ld3Hks5usCgggaJpZM4YOTeE>
.
|
Having all the notes from different WG's in one repository makes it a lot harder for people to follow just the WG's they care about :( |
I haven't checked out the other repo yet, so for my use-case, I'm not sure
it will be harder to follow along, or make it easier to find out about
other things happening. Which might be awesome learnings, or totally
distracting :)
…On Mon, Nov 5, 2018 at 7:59 PM Mikeal Rogers ***@***.***> wrote:
Having all the notes from different WG's in one repository makes it a lot
harder for people to follow just the WG's they care about :(
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#130 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADDt3-zz0IMcOPd6bIxzWanDJ0ramhqks5usIqQgaJpZM4YOTeE>
.
|
@autonome @mikeal No need to change your habits :) My plan is to continue publishing issues for weekly sync in this repo ( ps. I've been thinking about having a single issue instead of creating one-per-week – would that make things easier to follow (less noisy perhaps), or it is ok as it is now (each week == separate issue)? ps2. Let's delay the move until one or two more weeks, so we have time to discuss. |
Either way, I need to click through to find the actual notes themselves, so
doesn't matter much to me :)
…On Tue, Nov 6, 2018 at 9:37 PM Marcin Rataj ***@***.***> wrote:
@autonome <https://github.com/autonome> @mikeal
<https://github.com/mikeal> No need to change your habits :) My plan is
to continue publishing issues for weekly sync in this repo (
ipfs/in-web-browsers), they will include link to meeting notes, so there
is no need to watch anything else.
ps. I've been thinking about having a single issue instead of creating
one-per-week – would that make things easier to follow (less noisy
perhaps), or it is good as it is now (each week == separate issue)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#130 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADDt-GZ2ywlJTr9f6ILoUdJZnE6KPHfks5usdb0gaJpZM4YOTeE>
.
|
ipfs/in-web-browsers#130 License: MIT Signed-off-by: Marcin Rataj <lidel@lidel.org>
Final update: To minimize notification noise in this repo (and in general) we've moved meeting updates to:
If you want to follow weekly meeting notes, subscribe to that one issue :) |
All other WGs moved to:
https://github.com/ipfs/pm/tree/master/meeting-notes/2018
During #127 we decided to do the same.
The text was updated successfully, but these errors were encountered: