MiriamEspanaAcebal

Differences between revisions 13 and 14
⇤ ← Revision 13 as of 2023-06-28 11:54:19 →
Size: 15207
Editor: mirespace
Comment:
← Revision 14 as of 2023-06-28 11:56:58 → ⇥
Size: 15279
Editor: mirespace
Comment:
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
The first OS I used was DR-DOS (from Digital Research) on my NEC-V20 based PC, without HD, CGA graphics (only 4 colours!) ... I remember having a lot of fun with it and learning a lot about files and directories, commands (why should I be fearful of a black screen?), batch files and loaders: yes, I have to admit it was all for gaming, so I copied BASIC code from magazines (learning to code by intuition, guessing what those lines with repeated words were intended to do).   The first OS I used was DR-DOS (from Digital Research) on my NEC-V20 based PC, without HD, CGA graphics (only 4 colours!) ... I remember having a lot of fun with it and learning a lot about files and directories, commands (why should I be fearful of a black screen?), batch files and loaders: yes, I have to admit it was all for gaming, so I copied BASIC code from magazines (learning to code by intuition, guessing what those lines with repeated words were intended to do)... ahh... and how much you learned from the boot when a virus appeared!.

Launchpad ID:

mirespace

IRC:

mirespace

Email:

[email protected]

Timezone:

CET (UTC+01:00)

About Me

Hi! I'm Miriam. I'm a Computer Science Engineer that has been a Linux user since I installed my first SuSE 4.0 at the University (I remember I spent 5 days on it, using 5 DVDs from a Tech Linux Magazine!). I went through Fedora, CentOS, RedHat, Mandriva, LinuxMint, SuSE -again-, Debian and Ubuntu :).

The first OS I used was DR-DOS (from Digital Research) on my NEC-V20 based PC, without HD, CGA graphics (only 4 colours!) ... I remember having a lot of fun with it and learning a lot about files and directories, commands (why should I be fearful of a black screen?), batch files and loaders: yes, I have to admit it was all for gaming, so I copied BASIC code from magazines (learning to code by intuition, guessing what those lines with repeated words were intended to do)... ahh... and how much you learned from the boot when a virus appeared!.

I've been working at Canonical since Jul'21. Happy to be here :).

Team Memberships

Future Plans & Projects

  • Ubuntu Being an Ubuntu Core Dev member

Current Project & Goals

  • Ubuntu Being an Ubuntu Server Dev member

Contributions to the Ubuntu Community

I'm my road to be a Server-Dev, I have been doing the following things which I'm proud of:

Distro Packaging

Wiki/Manuals

I've edited and made contributions to following pages...

  • Ubuntu Explaining timers for unattended-upgrades at Discourse

    Ubuntu Ubuntu Maintainers Handbook - it's used in Server Team onboarding mainly, but also in other teams- :

Bug triage/Comments

I've been interacting in this list of bugs on launchpad. Most of them as part of the work for the BugHouseKeeping task that is done on the Server Team. Some of them worth mentioning are:

Contributions to the Open Source Community

Debian

Comments

If you'd like to comment, but are not the applicant or a sponsor, do it here. Don't forget to sign with @SIG@.

Endorsements

Bryce Harrington

General Feedback

I've worked with Miriam on the Canonical Server Team. She's been a pleasure to work with and is diligent at following up on suggestions to make sure her work is done with good care. I particularly appreciate her work on drafting documentation on team processes.

Specific Experiences of Working Together

As one of her first projects after joining Canonical, Miriam developed a thorough set of autopkgtests for logwatch, leveraging test case work done in recent SRUs for that package. These tests dealt with logs from a variety of other source packages beyond logwatch, including the kernel, apparmor, sshd, and su. Since her timezone and mine don't overlap very much, she was resourceful in also seeking out advice from other packagers for questions. She took all our feedback in stride and used it to incrementally improve the scripts to the point of readiness for my sponsorship of the Ubuntu upload. Logwatch was pretty severely lacking in testing previously, so she's achieved a very welcome improvement for the package.

I also sponsored an SRU for monitoring-plugins, to correct an issue introduced in a prior SRU of mine. This was a bit of a challenge because it required not only fixing the newly reported issue but doing so in a way that did not regress the previous fix, and hopefully would not introduce any other regressions. She also took into account upstream's views in developing the new fix, to potentially come up with a more universally acceptable solution. To support this work she developed a very thorough set of paint-by-numbers SRU test cases to demonstrate the fix's behavior in known use cases.

Areas of Improvement

You're building a great resume of work towards your objective of applying for Server Dev PPU; you've got good breadth of exposure to the required packaging skills and are focused on growing your depth and confidence levels in those skills. I'd particularly encourage growing depth in bug triaging and MP reviews. I think you're at a good point where you can start asking for endorsements as you continue doing more merges, SRUs, et al.

While maybe not required for PPU, I'd also suggest getting some exposure on +1 maintenance. For example you could ask to shadow someone in your timezone for a day during their +1 rotation for a day; this can be a great way to learn a lot of details about how the archive works.

Towards your future goal of CoreDev, I would encourage seeking out packaging opportunities beyond the server team. The Merge-o-Matic page can be quite helpful here. Keep in mind many packages outside server will not be using git-ubuntu for merges, so this will be an opportunity to learn alternative merge techniques.

CoreDev applicants are also required to have sponsorship endorsements outside their immediate team. To that end, even as you work on your PPU application, try to seek out reviewers outside our team who can sponsor your work, so you can request their endorsements later.

-- bryce 2022-02-04 23:09:20

As a sponsor, just copy the template below, fill it out and add it to this section.

TEMPLATE

== <SPONSORS NAME> ==
=== General feedback ===
## Please fill us in on your shared experience. (How many packages did you sponsor? How would you judge the quality? How would you describe the improvements? Do you trust the applicant?)

=== Specific Experiences of working together ===
''Please add good examples of your work together, but also cases that could have handled better.''
## Full list of sponsored packages can be generated here:
##  https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi
=== Areas of Improvement ===

CategoryHomepage

MiriamEspanaAcebal (last edited 2024-12-12 11:49:05 by mirespace)