This is the P2PU Archive. If you want the current site, go to www.p2pu.org!
You haven't posted any discussions yet.
This thread is intented for all your queires, concerns and also if any suggestions.
[As per the plan the course will begin on Web Sep 15 15:00 UTC 2010.]
Sorry, I can't assist at that time, i'm in UTC-4 so it's 11. Work time :/. Are the logs going to be saved?
Ditto for no show (I'm in UTC-4 as well). Hopefully we can vary the meet times (if possible). Thanks for running this course.
Where are you from? Y hablas español supongo o no?
yo? soy de Venezuela
Latinoamérica presente :)
Marcos, de Argentina.
Hahaha así es! Chile Presente :P
Saludos, Colombia presente tambien.
That's like 9 am for me, so that works!
I work long hours so I'll be playing catch up at the end of the day. Hoping the days events will be logged...
Too much variation in time zones, its time to make a poll!
I think I missed it, was there a log made?
Did you do the reunion?
There was a poll made on the timings, i don't know if it reached all or not, but there was a broadcast made, here is the poll link http://is.gd/fbAG1 Very soon the apt timings and day will be announced. Probability of the course kicking off today is high based on the current status of the poll.
Hi, has anything happened so far? I am in UTC +10 so the suggested timings are too late in the night.. I might have to catch up later on too. Looking forward to the first call for action :)
59% of them have voted for weekends, UTC 15:30 seems to the time that most of them have agreed, so that is the best i feel, so we will have an awesome start on Sat Sep 18 15:30:00 UTC 2010. So gear up by then, indeed after all it's P2P we will have loads to learn and teach :0)
Hi, what's the URL for the webinar at UTC 15.30 please? If an email went round with the details I din't receive it. Cheers.
Mail was broad-casted to the group, but its not been dispatched to the all, some minor issue with the mail server.
The class URL -> http://p2pu.org/node/5686/chat and the time is *Sat Sep 18 15:30:00 UTC 2010*
Is there a schedule of next sessions?
Read the logs if you have missed them :
Class 1 -> http://p2pu.org/scripting-101/document/chat-log-class-1
Class 2 -> http://p2pu.org/scripting-101/document/chat-log-class-2
Class 3 scheduled on Sat Sep 25 15:30 UTC 2010
Thanks, I read them. I will make my git brunch to begin participating. Do you think is better make my presentation here or wait till the next irc meeting?
You can go ahead, need not wait for the next class, do make a new thread about what ever you want to present.
I somewhat have a stupid question that I've been holding back... I'm really bad with time, I guess something wrong with the way my brain works. For instance I can hardly remember the order of the months. But anyways i'm not sure how to convert "UTC 15:30" into my time...
By the way I'm not stupid LOL. I just can't work with time very well. Programming I can do, time nope.
Thanks
@Isaiah Gilliland Nice, that is a good trait of a good programmer :D
Now in your GNU/Linux terminal type date -u the output you notice is the UTC time based on it calculate.
Still more, date -u '+%H : %M : %S' is the GMT time now and date '+%H : %M : %S' is your time :)
To get the start time of the class, its always been messy for most of us, so made a simple script to make things easier all you have to do is open your .bashrc, with either 'emacs ~/.bashrc' or 'vim ~/.bashrc' or any editor and paste the code below
function class(){
day1=$(date -d "next saturday" +%Y-%m-%d )
day2=$(date -d "next sunday" +%Y-%m-%d )
time=$(date -d "15:30 UTC" +%H:%M)
echo "See you on $day1 and $day2 at $time on http://p2pu.org/node/5686/chat"
}
After saving and exiting, you need to type bash and hit enter, from now own whenever you open your terminal, you can just type "class" [ without quotes] and hit enter to see when the next class will be.
By the way how do we actually turn in our work? Do we use Git? I'm not really knowledgeable about source code management.
Yes, first you need to fork the repo from github and then add your source code and sent me a pull request, ok putting it in easy steps, assuming you are on a Debian based OS, follow the steps as below:
Forking the repo : http://help.github.com/forking/
In your terminal type in each line :
sudo apt-get install git-core
git clone
cd p2pu/variables/bash
touch variables.bash # The file where you will be adding your code
git add variables.bash
git push origin master
You're supposed to fork the repo and then clone your own forked-repo? Because I did clone the original (I don't mind doing it again, just asking).
Yes fork the repo, clone the repo you forked, commit and push and sent a pull request :)
o.o See I'm not even sure what forking and cloning is. Never learned about these in college either, I feel really cheated lol. I found a git book, I'll try to catch up on my own. I need to learn this if I want to be serious about it.
Now do you have to add every single new thing before pushing? Or is there an easier way to add anything new? This is for future reference :D
Though a bad practice, one can do :
git add *
git push
git commit -m "Added everything"
Cheat sheet => http://is.gd/fumLw
Shouldn't the commit command come prior to push?
git commit -m "Added everything"
git push
?
Yes even better to do "git push origin master", in case you are having different branches. Commit before push. because we need to commit comment on every push, only those which have been added with git add, gets pushed. So its always better to add each file individually, cause some editors will have tmp buffer with filename~, so saying git add *, will add them also to the repo!