[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-kimageshop
Subject: Re: Welcome to all students
From: Wolthera <griffinvalley () gmail ! com>
Date: 2018-04-25 3:33:31
Message-ID: CAN80MtGZq-ZWN13=nJ7SZ0zB35PkQyAJU7NUucMhQpRp0vx+Zw () mail ! gmail ! com
[Download RAW message or body]
Yes, you can setup the feed to use a subcategory, I use the tag KDE for
mine.
For tasks, make a main task tagged with the project Krita. You can make
subtasks to that main task as you see fit. The main purpose of a task is to
make the bureaucracy at the end simpler. Because when you commit, you can
put "Ref T###" (T### being your main task), and then when the commit is
pushed, phab will add a note about it to the task.
As for commit access, if you ever have pushed there's a good change you
still have commit access. I guess the next step is to make new ssh keys and
add them to the dash at identity.kde.org.
Good luck!
On Wed, 25 Apr 2018, 03:04 Iván Yossi, <ghevan@gmail.com> wrote:
> Hello!
>
> Reporting for duty :3, Im so happy I was accepted, now comes the hardwork!
> Now some questions regarding initial setup.
>
> In KDE identity I'm still part of the Group named «developers », so probaly
> I still hace writing access, but im not exactly sure if that is enough to
> assert that I have writting permissions.
>
> Second: for the master task you use the term "master" as a "parent" for
> all our tasks? if so does it suffice to create a Task under
> Tasks > create Tasks
>
> As for the monday meetings: Moday meetings schedule works good for me, In
> any cas I cannot attend I will tell about it beforehand. But priority is
> with the meeting as I can normally attend it.
> About the blog, I just read about the process of adding a blog to the
> platform, seems easy enough. So I'll make sure to setup a blog with RSS for
> this to work. As a question, could the syndicated blog be a sub-blog of a
> bigger blog site? (Im sure RSS can be served just for subcats, not so sure
> if wordpress allows it and if its desirable to have the content as a
> subblog of another personal blog) If not, so i can setup a dedicated blog
> just for the GSoc progress.
>
> Thanks!!
> Iván
>
>
> On Apr 24, 2018, 09:11 -0500, Scott Petrovic <scottpetrovic@gmail.com>,
> wrote:
>
> Congratulations to all of you for being accepted. You will be learning a
> lot in the coming months! Boud is at a conference for a bit, but there are
> still people hanging out on IRC. Feel free to come by if you have any
> questions. https://krita.org/en/irc/ There are other IRC clients, but
> that is a quick way to get you started if you aren't sure how to connect.
>
> Most of the developers are on IRC daily. If you want to ask questions and
> absorb how Krita works, I would highly recommend staying on Krita's IRC
> channel as much as possible. There is quite a bit of developer talk as well
> as support related things that are discussed to learn how things work.
>
> Best
> Scott (IRC: scottyp2 or scottyp)
>
>
>
>
> On Tue, Apr 24, 2018 at 2:19 AM, Boudewijn Rempt <boud@valdyas.org> wrote:
>
>> Hi Yvan, Michael, Andrey!
>>
>> Welcome to the Google Summer of Code with Krita! I'm really happy that
>> we've
>> managed to get all three of you on board and I'm looking forward to
>> working
>> with you all!
>>
>> Note that this week I'm at the Libre Graphics Meeting: I will be around
>> on IRC
>> a bit, and I will be available by mail, too.
>>
>> Here are a couple of getting-started points:
>>
>> * All of you already have push access to the git repo, right? If not, make
>> sure you get that asap.
>>
>> * Please do make sure that you get started with creating a phabricator
>> master
>> task for your work.
>>
>> * We will start having weekly Monday 14:00 CEST meetings again from 8 May.
>>
>> If that doesn't work for you because of timezone issues, please do say so
>> on
>> this list: we can schedule a second meeting later in the day, but we
>> should
>> have a start-of-the-week synchronizing meeting to make sure everything is
>> going well.
>>
>> * You should also blog regularly about your work, and your blog should be
>> syndicated to planetkde
>>
>> That's all for now!
>>
>> --
>> Boudewijn Rempt | https://www.krita.org
>>
>>
>>
>
[Attachment #3 (text/html)]
<div dir="auto">Yes, you can setup the feed to use a subcategory, I use the tag KDE \
for mine.<div dir="auto"><br></div><div dir="auto">For tasks, make a main task tagged \
with the project Krita. You can make subtasks to that main task as you see fit. The \
main purpose of a task is to make the bureaucracy at the end simpler. Because when \
you commit, you can put "Ref T###" (T### being your main task), and then \
when the commit is pushed, phab will add a note about it to the task.</div><div \
dir="auto"><br></div><div dir="auto">As for commit access, if you ever have pushed \
there's a good change you still have commit access. I guess the next step is to \
make new ssh keys and add them to the dash at <a \
href="http://identity.kde.org">identity.kde.org</a>.</div><div \
dir="auto"><br></div><div dir="auto">Good luck!</div></div><br><div \
class="gmail_quote"><div dir="ltr">On Wed, 25 Apr 2018, 03:04 Iván Yossi, <<a \
href="mailto:ghevan@gmail.com">ghevan@gmail.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
<div>
<div name="messageBodySection" \
style="font-size:14px;font-family:-apple-system,BlinkMacSystemFont,sans-serif">Hello! \
<div><br></div> <div>Reporting for duty :3, Im so happy I was accepted, now comes the \
hardwork! Now some questions regarding initial setup.</div> <div>
<div><br></div>
<div>In KDE identity I'm still part of the Group named «developers », so probaly I \
still hace writing access, but im not exactly sure if that is enough to assert that I \
have writting permissions.</div> <div><br></div>
<div>Second: for the master task you use the term "master" as a \
"parent" for all our tasks? if so does it suffice to create a Task \
under</div> <div><span class="m_-7047693785846289706Apple-tab-span" \
style="white-space:pre-wrap"></span>Tasks > create Tasks</div> <div><br></div>
<div>As for the monday meetings: Moday meetings schedule works good for me, In any \
cas I cannot attend I will tell about it beforehand. But priority is with the meeting \
as I can normally attend it.</div> <div><span \
class="m_-7047693785846289706Apple-tab-span" \
style="white-space:pre-wrap"></span></div> <div><span \
class="m_-7047693785846289706Apple-tab-span" \
style="white-space:pre-wrap"></span>About the blog, I just read about the process of \
adding a blog to the platform, seems easy enough. So I'll make sure to setup a \
blog with RSS for this to work. As a question, could the syndicated blog be a \
sub-blog of a bigger blog site? (Im sure RSS can be served just for subcats, not so \
sure if wordpress allows it and if its desirable to have the content as a subblog of \
another personal blog) If not, so i can setup a dedicated blog just for the GSoc \
progress.</div> </div>
<div><br></div>
<div>Thanks!!</div>
<div>Iván</div>
<div><br></div>
</div>
<div name="messageReplySection" \
style="font-size:14px;font-family:-apple-system,BlinkMacSystemFont,sans-serif"><br> \
On Apr 24, 2018, 09:11 -0500, Scott Petrovic <<a \
href="mailto:scottpetrovic@gmail.com" target="_blank" \
rel="noreferrer">scottpetrovic@gmail.com</a>>, wrote:<br> <blockquote type="cite" \
style="margin:5px 5px;padding-left:10px;border-left:thin solid #1abc9c"> <div \
dir="ltr"> <div>Congratulations to all of you for being accepted. You will be \
learning a lot in the coming months! Boud is at a conference for a bit, but there are \
still people hanging out on IRC. Feel free to come by if you have any questions. <a \
href="https://krita.org/en/irc/" target="_blank" \
rel="noreferrer">https://krita.org/en/irc/</a> There are other IRC clients, but \
that is a quick way to get you started if you aren't sure how to connect.</div> \
<div><br></div> <div>Most of the developers are on IRC daily. If you want to ask \
questions and absorb how Krita works, I would highly recommend staying on Krita's \
IRC channel as much as possible. There is quite a bit of developer talk as well as \
support related things that are discussed to learn how things work. </div> \
<div><br></div> <div>Best</div>
<div>Scott (IRC: scottyp2 or scottyp)</div>
<div><br></div>
<div><br></div>
<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Apr 24, 2018 at 2:19 AM, Boudewijn Rempt <span \
dir="ltr"><<a href="mailto:boud@valdyas.org" target="_blank" \
rel="noreferrer">boud@valdyas.org</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:5px 5px;padding-left:10px;border-left:thin solid \
#e67e22">Hi Yvan, Michael, Andrey!<br> <br>
Welcome to the Google Summer of Code with Krita! I'm really happy that \
we've<br> managed to get all three of you on board and I'm looking forward to \
working<br> with you all!<br>
<br>
Note that this week I'm at the Libre Graphics Meeting: I will be around on \
IRC<br> a bit, and I will be available by mail, too.<br>
<br>
Here are a couple of getting-started points:<br>
<br>
* All of you already have push access to the git repo, right? If not, make<br>
sure you get that asap.<br>
<br>
* Please do make sure that you get started with creating a phabricator master<br>
task for your work.<br>
<br>
* We will start having weekly Monday 14:00 CEST meetings again from 8 May.<br>
<br>
If that doesn't work for you because of timezone issues, please do say so on<br>
this list: we can schedule a second meeting later in the day, but we should<br>
have a start-of-the-week synchronizing meeting to make sure everything is<br>
going well.<br>
<br>
* You should also blog regularly about your work, and your blog should be<br>
syndicated to planetkde<br>
<br>
That's all for now!<br>
<span class="m_-7047693785846289706gmail-m_-4447538546287382283HOEnZb"><font \
color="#888888"><br>
--<br>
Boudewijn Rempt | <a href="https://www.krita.org" rel="noreferrer noreferrer" \
target="_blank">https://www.krita.org</a><br> <br>
<br></font></span></blockquote>
</div>
<br></div>
</div>
</blockquote>
<div></div>
</div>
</div>
</blockquote></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic