search

peerlibrary / outreach

PeerLibrary outreach
https://peerlibrary.org/
8 stars 4 forks source link

GoogleDoc Bay Area Open Access report #153

Closed gar-bear closed 10 years ago

gar-bear commented 10 years ago

I am to do it.

gar-bear commented 10 years ago

It has been done; awaiting Mitar's email respons for it to be put in PeerLibrary folder.

mitar commented 10 years ago

Please assign milestones and labels next time.

Add document into PeerLibrary folder. I cannot access it. So no need to wait, just put it immediately into the folder.

gar-bear commented 10 years ago

Yes, the problem is that I cannot add it into the PeerLibrary folder. Can you describe how to do that?

gar-bear commented 10 years ago

I have dropped it into the Event Reports subfolder under Conferences & Events. It looks legit on my end, so I will close it if there are no objections.

mitar commented 10 years ago

Perfect.

mitar commented 10 years ago

I would question the logic of putting event reports into Google Drive. We work in open. I think that any criticism of events, both positive or negative, and our experience of them can be public. So using closing comments on tickets would be better. Like you did before.

gar-bear commented 9 years ago

Sorry, this email slipped past me. I was told by Rachel to post it into a GoogleDoc, should I not do that next time?

On Tue, Nov 25, 2014 at 5:14 AM, Mitar notifications@github.com wrote:

I would question the logic of putting event reports into Google Drive. We work in open. I think that any criticism of events, both positive or negative, and our experience of them can be public. So using closing comments on tickets would be better. Like you did before.

— Reply to this email directly or view it on GitHub https://github.com/peerlibrary/outreach/issues/153#issuecomment-64397443 .

Gary Richmond Zero Waste Research Center Program Associate The Green Initiative Fund

_LEAD Center | _ASUC Student Union | University of California, Berkeley 102 Hearst Gym MC 4500 | Berkeley CA 94720-4500 e. gar-bear@berkeley.edu | tgif.berkeley.edu http://tgif.berkeley.edu/ Follow us: Facebook https://www.facebook.com/thegreeninitiativefund | Twitter https://twitter.com/TGIF_UCB | Newsletter http://us3.campaign-archive1.com/home/?u=8c4a45c0abc1f3bf1b36e8919&id=f5b8cfc4ae

mitar commented 9 years ago

I am opening it for the discussion. I personally would prefer in the comments and am suggesting that.

Of course there might be some private things to share, but we could use some other channels to share that. Just because there might be occasional private information in reports we should not by default make everything private.

You did nothing wrong. We just haven't discussed this before. :-) Rachel recommended something, I recommend something else. None of this is really problematic, so don't worry. Let's discuss it at next meeting how we should be doing this.

raaswol commented 9 years ago

I said this so that we can access it in a devoted directory later, to browse. Nothing to do with privacy. I didn't say NOT to post in github, but to ALSO post in drive, additionally. The link idea saves time, but there was no other reason for it.

Good point though, there's sometimes sensitive info in there. I'll put it in tomorrow's agenda.

mitar commented 9 years ago

Ah, I just search GitHub tickets to find the tickets. :-) We could also also use "report" label on GitHub to mark those tickets which have a report. But I am just used that every ticket has a report at the end, reporting on what has been done. So if you are searching for something, you just search for that ticket and read at the end.

raaswol commented 9 years ago

but what if you want to look through every event we ever attended, and not scroll and switch pages? you can just look at the events>reports folder and open them simultaneously if you want, or at least keep the folder open while you read. plus, git tickets often get lost in spelling differences, missing or extra spaces, or naming being unknown

mitar commented 9 years ago

Then you open a list of tickets labeled "conference or event". :-) If we use labels correctly, then it works.

So what I am saying is: we should try to keep as much of information as possible in GitHub. This should be our main point of information, organization, and search. We can link from here to Google Drive for few documents, but this should be our main point: it is public, it is visible to everyone, and can serve multiple uses.

We are currently underusing GitHub a lot. And this is why it is not as useful as it could be. We will learn.

git tickets often get lost in spelling differences, missing or extra spaces, or naming being unknown

Yes, that's why we should write titles well. :-)