From: "Gábor Boskovits" <boskovits@gmail.com>
To: Laura Lazzati <laura.lazzati.15@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: [outreachy] am I in the right track to contribute
Date: Thu, 11 Oct 2018 11:24:36 +0200 [thread overview]
Message-ID: <CAE4v=pgCu15z4S2t5MJQjm9VrC8VsAddS3eON-u9jijCQGGWpg@mail.gmail.com> (raw)
In-Reply-To: <CAPNLzUPShmkAjyqX9KYmFTMvCm=vN7M=H2n82=A8s+JY4K+U6A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6929 bytes --]
Hello Laura,
Laura Lazzati <laura.lazzati.15@gmail.com> ezt írta (időpont: 2018. okt.
11., Cs, 3:25):
>
> On Wed, Oct 10, 2018 at 3:12 PM Gábor Boskovits <boskovits@gmail.com>
wrote:
> >
> >
> > Hello Laura,
> >
> > Laura Lazzati <laura.lazzati.15@gmail.com> ezt írta (időpont: 2018.
okt. 10., Sze 18:41):
> >>
> >> On Tue, Oct 9, 2018 at 1:17 PM Björn Höfling
> >> <bjoern.hoefling@bjoernhoefling.de> wrote:
> >> >
> >> > Hi Laura,
> >> >
> >> > On Tue, 9 Oct 2018 10:08:44 -0300
> >> > Laura Lazzati <laura.lazzati.15@gmail.com> wrote:
> >> >
> >> > > Hi everyone!
> >> > >
> >> > > I don't know if is it OK to be telling you what I am/ I've been
doing
> >> > > these days, I kind of like doing so to have feedback, and also to
let
> >> > > you know
> >> >
> >> > This is exactly the way to go! It's good to hear where you stay, what
> >> > you tried, where you succeeded, where you got stuck. If you get
stuck,
> >> > tell us about the paths you already tried out and why you don't get
> >> > further alone.
> >> >
> >> Sorry for being absent for a day. After updating and upgrading my
> >> computer, I am stuck trying to see why the sound stopped working. Yes,
> >> this kind of thinks happen but just now?
> >
> >
> > No worries, one day off is perfectly ok, however if you did not get an
answer in 3 or 4 days, then please contact us, since in that case there is
some communications mistake.
> > Last time losing sound happened to me after a dist-upgrade in ubuntu,
and turned out, that the pulseaudio package shipped with a configuration
that was not compatible with the version of the binaries supplied. I ran it
in the foreground, and in the startup messages or in the log I found that
it could not parse the config. It can be something entirely different
though. I hope this helps.
>
> Thanks :) Unluckily i made a mistake and ended up needing a fresh
> install. But I am the kind of person that always has data backup and
> is aware of the software and utilities that needs. Tomorrow I will go
> on with my VMs, the one with only Guix, and one with GuixSD and start
> with the package stuff, so that I can contribute as much as I can,
> even if I am not chosen for outreachy.
Sorry to hear that, but glad that you did not suffer any data loss.
Having the VMs back by tomorrow is nice, thanks for the update.
> >>
> >>
> >> > One thing that was today on the Outreachy mentors-mailinglist: If you
> >> > finally made a contribution, please go directly on the Outreachy
> >> > project page, select the Guix project and formally record your
> >> > contributions. That's important to us and for the whole Outreachy
> >> > project to see who/how many applicants are possible candidates for a
> >> > project
> If I do the R packaging, where do I record in Guix? And I am keeping
> my daily journal with the problems I encounter, but I am not very sure
> about where to upload it for Guix. As regards my daily journal. is it
> OK to hace it in Google Drive? I know its FOSS, but it's a good way of
> easily updating the doc and having it accesible. And in outreachy it
> says that Refining current documentation is a contribution too. I
> don't know if this applies also to problems I encounter and how I
> managed to solve them.
>
If you have a working package, and you followed the contribution guide, you
got to the part
where you can send your patch. The debbugs issue tracker creates an issue
for the patches
sent to guix-patches@gnu.org. These patches are then reviewed, we will give
you feedback,
and when it is in a shape to include it in guix, we will accept it,
upstream the changes and close
the issue. This completes the contibution. Then you will have to record
this on the Outreachy site.
https://www.outreachy.org/apply/
in this point:
4. Record in-progress contributions on the Outreachy website
<https://www.outreachy.org/apply/project-selection/>. You'll need to go to
the community landing page linked from the projects listing page
<https://www.outreachy.org/apply/project-selection/>. Then click the
'Record Contribution' button. Add links and descriptions to your
contributions and the project timeline before the application deadline. You
can always go back and edit your recorded contributions. A contribution
doesn't have to be merged or accepted to be recorded.
describes the process.
Note that you can record the contibution while it is still in progress.
You can get faster responses if you CC your mentors to the message sent to
guix-patches, so that we can notice the incoming patch.
For now I suggest sending the notes with the difficulties encountered in a
mail to the devel list, accompanied with suggestions on how to clarify the
relevant parts of the documentation. Documentation changes tend to take
longer, as it usually involves community discussion, but you can get this
started. You can keep your private copy of these on google drive, and it is
possible to create a git repo somewhere to keep track of a file with these,
preferably an org mode text document.
WDYT?
> See the "Application Setup" section in the manual, for more info.
>
>
>
>
>
> >> >
> >> >
> >> > > I installed guix on a VM with an Ubuntu distro and it worked fine
- i
> >> > > ran some basic commands.
> >> > > I am trying to install GuixSD over that VM too and on bare metal -
> >> > > don't know if this two steps are necessary, but looking at the
tasks
> >> > > for Outreachy one items says that I will be doing documentation for
> >> > > it.
> >> >
> >> > Concerning bare metal: Guix uses 100% Free Software und thus uses the
> >> > libre kernel, not the normal vanilla kernel. That means some binaries
> >> > included in the vanilla kernel are stripped off. Hickups might occur,
> >> > especially with Network, WLAN and Graphics, compared to Ubuntu.
> >> >
> >> I thought that by installing bare metal ment installing it on a VM
> >> without any operating system. I mean, putting the ISO there. I only
> >> have one retro PC available with no OS where I could be trying that -
> >> it is like 13 years old, and it is not a laptop.
> >
> >
> > It is ok to skip that all together, a VM install is more than enough
for now.
> >
> >> > As always before installing a new OS, make backups of your data and
> >> > configurations on that machine!
> >> >
> >> > > 1) should I write, at least for myself, the problems I've been
> >> > > encountering in the whole process of doing everything?
> >> >
> >> > Yes, very good! I do that for myself too. It leads to good,
reproducible
> >> > bug reports, bug fixes, documentation fixes, blog entries and could
also
> >> > be used as a starting point for a screenplay for the videos.
> >> Love doing this kind of things.
> >> >
> >> > Björn
> >
> > Best regards,
> > g_bor
Best regards,
g_bor
[-- Attachment #2: Type: text/html, Size: 8687 bytes --]
next prev parent reply other threads:[~2018-10-11 9:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 13:08 [outreachy] am I in the right track to contribute Laura Lazzati
2018-10-09 16:17 ` Björn Höfling
2018-10-10 16:41 ` Laura Lazzati
2018-10-10 18:12 ` Gábor Boskovits
2018-10-11 1:24 ` Laura Lazzati
2018-10-11 9:24 ` Gábor Boskovits [this message]
2018-10-11 14:31 ` Laura Lazzati
2018-10-11 17:05 ` Gábor Boskovits
2018-10-11 17:40 ` Leo Famulari
2018-10-11 19:57 ` Laura Lazzati
2018-10-12 6:31 ` Gábor Boskovits
2018-10-12 12:35 ` Laura Lazzati
2018-10-11 18:55 ` Björn Höfling
2018-10-11 19:06 ` Ricardo Wurmus
2018-10-11 19:07 ` Gábor Boskovits
2018-10-09 22:25 ` Alex Vong
2018-10-10 16:44 ` Laura Lazzati
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=pgCu15z4S2t5MJQjm9VrC8VsAddS3eON-u9jijCQGGWpg@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=laura.lazzati.15@gmail.com \
--cc=ricardo.wurmus@mdc-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.