From gerv at mozilla.org Mon Sep 2 15:48:45 2013 From: gerv at mozilla.org (Gervase Markham) Date: Mon, 02 Sep 2013 16:48:45 +0100 Subject: Bugzilla docs: test conversion to RST and hosting on readthedocs.org In-Reply-To: References: Message-ID: <5224B35D.1030409@mozilla.org> On 31/08/13 20:51, Colin Ogilvie wrote: > I did find a more up-to-date db2rst script > at https://github.com/kurtmckee/db2rst which might help? I've not tried > it as I'm not sure what changes you'd made in the first place. Thanks for the tip - although the amount of data is small enough and the current script is good enough that I think that, if we decide to switch, we should just run the current script and then fix up the result by hand and never use it again... > The index issue: we could probably hard-code the generation of the list, > or at least work on a sort order... a quick 5 minute play has got me > generating an index, but it's not ideal :-) I think Sphinx has contents auto-generation that we could use if we hook it all up properly. Gerv From gerv at mozilla.org Tue Sep 3 10:36:36 2013 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 03 Sep 2013 11:36:36 +0100 Subject: Bugzilla docs: test conversion to RST and hosting on readthedocs.org In-Reply-To: References: Message-ID: <5225BBB4.7060800@mozilla.org> On 31/08/13 14:35, Gervase Markham wrote: > Further to pervious emails on the subject, I've hacked up something to > convert the Bugzilla docs from Docbook to RST (ReStructured Text), > uploaded them to Github and connected the Github repo to readthedocs.org. Anyone other than Colin have comments here? If we think this is the right way to go, I think we should: - Convert the trunk docs (only) in a one-off process - Patch them up so we have a TOC etc. (the conversion is not 100% perfect) - rewrite makedocs.pl to use Sphinx to build HTML, LaTeX -> PDF, and TXT (if the relevant converters are available) - Check this all in on trunk, using the directory docs/en/rst, and remove the XML versions and checked-in built versions - Point http://bugzilla.readthedocs.org at the trunk repo (RTD supports Bazaar, so we don't have to wait for any SCM shift) - (Optional) Add a post-commit hook to ping RTD to rebuild on checkin - Update the "HTML" and "PDF" links on http://www.bugzilla.org/docs/ to point to RTD; retain the "API" link; eliminate the "TXT" link If this sounds like a plan, I'll file some bugs. Gerv > It's hackily done, and one thing that hasn't come across is the TOC > (which is auto-generated when using Docbook). So there isn't an index > page. But you can see the results here: > > https://bugzilla.readthedocs.org/en/latest/about.html > https://bugzilla.readthedocs.org/en/latest/administration.html > https://bugzilla.readthedocs.org/en/latest/Bugzilla-Guide.html > https://bugzilla.readthedocs.org/en/latest/conventions.html > https://bugzilla.readthedocs.org/en/latest/customization.html > https://bugzilla.readthedocs.org/en/latest/gfdl.html > https://bugzilla.readthedocs.org/en/latest/glossary.html > https://bugzilla.readthedocs.org/en/latest/installation.html > https://bugzilla.readthedocs.org/en/latest/modules.html > https://bugzilla.readthedocs.org/en/latest/patches.html > https://bugzilla.readthedocs.org/en/latest/security.html > https://bugzilla.readthedocs.org/en/latest/troubleshooting.html > https://bugzilla.readthedocs.org/en/latest/using.html > > I'm sure there are style and conversion nits, but I think it's good > enough to evaluate whether this is the way we want to go. > > The advantages of this system is that RST is much easier to edit, Sphinx > can be installed locally (as one package) so that anyone hacking on the > docs can compile them themselves to HTML or other formats, and > readthedocs.org automatically takes care of making sure we have a lovely > web version. Because it's SCM-backed, we can have branches for each > version of Bugzilla, which was a requirement. And if and when Bugzilla > moves to Git, I'm pretty sure we can then simply keep the docs in the > same repo as the code. > > Comments? > > Gerv > _______________________________________________ > dev-apps-bugzilla mailing list > dev-apps-bugzilla at lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-apps-bugzilla > - > To view or change your list settings, click here: > > From justdave at bugzilla.org Tue Sep 3 11:01:08 2013 From: justdave at bugzilla.org (Dave Miller) Date: Tue, 03 Sep 2013 07:01:08 -0400 Subject: Bugzilla docs: test conversion to RST and hosting on readthedocs.org In-Reply-To: <5225BBB4.7060800@mozilla.org> References: <5225BBB4.7060800@mozilla.org> Message-ID: Sounds like a plan. I like it. Gervase Markham wrote: >On 31/08/13 14:35, Gervase Markham wrote: >> Further to pervious emails on the subject, I've hacked up something >to >> convert the Bugzilla docs from Docbook to RST (ReStructured Text), >> uploaded them to Github and connected the Github repo to >readthedocs.org. > >Anyone other than Colin have comments here? > >If we think this is the right way to go, I think we should: > >- Convert the trunk docs (only) in a one-off process > >- Patch them up so we have a TOC etc. (the conversion is not 100% > perfect) > >- rewrite makedocs.pl to use Sphinx to build HTML, LaTeX -> PDF, and >TXT > (if the relevant converters are available) > >- Check this all in on trunk, using the directory docs/en/rst, and > remove the XML versions and checked-in built versions > >- Point http://bugzilla.readthedocs.org at the trunk repo (RTD > supports Bazaar, so we don't have to wait for any SCM shift) > >- (Optional) Add a post-commit hook to ping RTD to rebuild on checkin > >- Update the "HTML" and "PDF" links on http://www.bugzilla.org/docs/ to > point to RTD; retain the "API" link; eliminate the "TXT" link > >If this sounds like a plan, I'll file some bugs. > >Gerv > >> It's hackily done, and one thing that hasn't come across is the TOC >> (which is auto-generated when using Docbook). So there isn't an index >> page. But you can see the results here: >> >> https://bugzilla.readthedocs.org/en/latest/about.html >> https://bugzilla.readthedocs.org/en/latest/administration.html >> https://bugzilla.readthedocs.org/en/latest/Bugzilla-Guide.html >> https://bugzilla.readthedocs.org/en/latest/conventions.html >> https://bugzilla.readthedocs.org/en/latest/customization.html >> https://bugzilla.readthedocs.org/en/latest/gfdl.html >> https://bugzilla.readthedocs.org/en/latest/glossary.html >> https://bugzilla.readthedocs.org/en/latest/installation.html >> https://bugzilla.readthedocs.org/en/latest/modules.html >> https://bugzilla.readthedocs.org/en/latest/patches.html >> https://bugzilla.readthedocs.org/en/latest/security.html >> https://bugzilla.readthedocs.org/en/latest/troubleshooting.html >> https://bugzilla.readthedocs.org/en/latest/using.html >> >> I'm sure there are style and conversion nits, but I think it's good >> enough to evaluate whether this is the way we want to go. >> >> The advantages of this system is that RST is much easier to edit, >Sphinx >> can be installed locally (as one package) so that anyone hacking on >the >> docs can compile them themselves to HTML or other formats, and >> readthedocs.org automatically takes care of making sure we have a >lovely >> web version. Because it's SCM-backed, we can have branches for each >> version of Bugzilla, which was a requirement. And if and when >Bugzilla >> moves to Git, I'm pretty sure we can then simply keep the docs in the >> same repo as the code. >> >> Comments? >> >> Gerv >> _______________________________________________ >> dev-apps-bugzilla mailing list >> dev-apps-bugzilla at lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-apps-bugzilla >> - >> To view or change your list settings, click here: >> >> >- >To view or change your list settings, click here: > -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerv at mozilla.org Tue Sep 3 14:59:35 2013 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 03 Sep 2013 15:59:35 +0100 Subject: Bugzilla docs: test conversion to RST and hosting on readthedocs.org In-Reply-To: References: <5225BBB4.7060800@mozilla.org> Message-ID: <5225F957.10005@mozilla.org> On 03/09/13 12:01, Dave Miller wrote: > Sounds like a plan. I like it. https://bugzilla.mozilla.org/show_bug.cgi?id=912064 . Gerv From mcote at mozilla.com Tue Sep 3 15:08:47 2013 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Tue, 03 Sep 2013 11:08:47 -0400 Subject: Bugzilla docs: test conversion to RST and hosting on readthedocs.org In-Reply-To: <5225BBB4.7060800@mozilla.org> References: <5225BBB4.7060800@mozilla.org> Message-ID: <5225FB7F.9040605@mozilla.com> I too love this. Another step in modernizing Bugzilla! :) Mark On 2013-09-03 6:36 AM, Gervase Markham wrote: > On 31/08/13 14:35, Gervase Markham wrote: >> Further to pervious emails on the subject, I've hacked up something to >> convert the Bugzilla docs from Docbook to RST (ReStructured Text), >> uploaded them to Github and connected the Github repo to readthedocs.org. > Anyone other than Colin have comments here? > > If we think this is the right way to go, I think we should: > > - Convert the trunk docs (only) in a one-off process > > - Patch them up so we have a TOC etc. (the conversion is not 100% > perfect) > > - rewrite makedocs.pl to use Sphinx to build HTML, LaTeX -> PDF, and TXT > (if the relevant converters are available) > > - Check this all in on trunk, using the directory docs/en/rst, and > remove the XML versions and checked-in built versions > > - Point http://bugzilla.readthedocs.org at the trunk repo (RTD > supports Bazaar, so we don't have to wait for any SCM shift) > > - (Optional) Add a post-commit hook to ping RTD to rebuild on checkin > > - Update the "HTML" and "PDF" links on http://www.bugzilla.org/docs/ to > point to RTD; retain the "API" link; eliminate the "TXT" link > > If this sounds like a plan, I'll file some bugs. > > Gerv > >> It's hackily done, and one thing that hasn't come across is the TOC >> (which is auto-generated when using Docbook). So there isn't an index >> page. But you can see the results here: >> >> https://bugzilla.readthedocs.org/en/latest/about.html >> https://bugzilla.readthedocs.org/en/latest/administration.html >> https://bugzilla.readthedocs.org/en/latest/Bugzilla-Guide.html >> https://bugzilla.readthedocs.org/en/latest/conventions.html >> https://bugzilla.readthedocs.org/en/latest/customization.html >> https://bugzilla.readthedocs.org/en/latest/gfdl.html >> https://bugzilla.readthedocs.org/en/latest/glossary.html >> https://bugzilla.readthedocs.org/en/latest/installation.html >> https://bugzilla.readthedocs.org/en/latest/modules.html >> https://bugzilla.readthedocs.org/en/latest/patches.html >> https://bugzilla.readthedocs.org/en/latest/security.html >> https://bugzilla.readthedocs.org/en/latest/troubleshooting.html >> https://bugzilla.readthedocs.org/en/latest/using.html >> >> I'm sure there are style and conversion nits, but I think it's good >> enough to evaluate whether this is the way we want to go. >> >> The advantages of this system is that RST is much easier to edit, Sphinx >> can be installed locally (as one package) so that anyone hacking on the >> docs can compile them themselves to HTML or other formats, and >> readthedocs.org automatically takes care of making sure we have a lovely >> web version. Because it's SCM-backed, we can have branches for each >> version of Bugzilla, which was a requirement. And if and when Bugzilla >> moves to Git, I'm pretty sure we can then simply keep the docs in the >> same repo as the code. >> >> Comments? >> >> Gerv >> _______________________________________________ >> dev-apps-bugzilla mailing list >> dev-apps-bugzilla at lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-apps-bugzilla >> - >> To view or change your list settings, click here: >> >> > - > To view or change your list settings, click here: > From michiel.beijen at gmail.com Wed Sep 4 05:59:35 2013 From: michiel.beijen at gmail.com (Michiel Beijen) Date: Wed, 4 Sep 2013 07:59:35 +0200 Subject: Password Hashes, Again In-Reply-To: <38798.1334581659@thrush.ravenbrook.com> References: <38798.1334581659@thrush.ravenbrook.com> Message-ID: On Mon, Apr 16, 2012 at 3:07 PM, Nick Barnes wrote: > There are good reasons, acknowledged by the ITRS, to suppose that a > number of these long-term exponential trends are going to peter out > over the next decade. Just chiming into this thread. I'm Michiel, I work for OTRS, we make an open source helpdesk system written in Perl. We've just implemented for our upcoming 3.3 release, which we just have out in beta, a password hashing mechanism using bcrypt and the CPAN module Crypt::Eksblowfish::Bcrypt. We generate a salt, hash the password and store the hash and the salt in the password field. This way we do not need new columns just to store the salt. Actually, bcrypt is optional, if you don't install the module it'll fall back to using SHA to generate the hashes. And of course, if there is a bcrypt hash in the database, you can only decrypt it using the bcrypt module. Plus, the method we chose allows for 'seamless upgrade' - if you have an existing OTRS system, and you switch bcrypt on, any existing password hashes will still work, but if you change your password or create a new user, that'll use bcrypt. This was pretty trivial to implement and I think it would be helpful for bugzilla as well, especially for larger installations. If anyone is interested, maybe I can provide a patch against bugzilla for the same. -- Michiel From reed at reedloden.com Wed Sep 4 06:12:05 2013 From: reed at reedloden.com (Reed Loden) Date: Tue, 3 Sep 2013 23:12:05 -0700 Subject: Password Hashes, Again In-Reply-To: References: <38798.1334581659@thrush.ravenbrook.com> Message-ID: <20130903231205.1b713d11.reed@reedloden.com> On Wed, 4 Sep 2013 07:59:35 +0200 Michiel Beijen wrote: > Plus, the method we chose allows for 'seamless upgrade' - if you have > an existing OTRS system, and you switch bcrypt on, any existing > password hashes will still work, but if you change your password or > create a new user, that'll use bcrypt. > > This was pretty trivial to implement and I think it would be helpful > for bugzilla as well, especially for larger installations. If anyone > is interested, maybe I can provide a patch against bugzilla for the > same. I basically wrote the majority of a patch to do just that a while ago, but I haven't had any time to drive it to completion. I welcome anybody who wants to take where I left off and get the patch fully tested and ready for review. https://bugzilla.mozilla.org/show_bug.cgi?id=672129 ~reed From michiel.beijen at gmail.com Wed Sep 4 06:50:25 2013 From: michiel.beijen at gmail.com (Michiel Beijen) Date: Wed, 4 Sep 2013 08:50:25 +0200 Subject: Password Hashes, Again In-Reply-To: <20130903231205.1b713d11.reed@reedloden.com> References: <38798.1334581659@thrush.ravenbrook.com> <20130903231205.1b713d11.reed@reedloden.com> Message-ID: Hi Reed, On Wed, Sep 4, 2013 at 8:12 AM, Reed Loden wrote: > I basically wrote the majority of a patch to do just that a while ago, > but I haven't had any time to drive it to completion. I welcome anybody > who wants to take where I left off and get the patch fully tested and > ready for review. > > https://bugzilla.mozilla.org/show_bug.cgi?id=672129 Ah, that's great. I missed that part of the discussion, sorry! -- Michiel From gerv at mozilla.org Wed Sep 4 08:15:24 2013 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 04 Sep 2013 09:15:24 +0100 Subject: Password Hashes, Again In-Reply-To: References: <38798.1334581659@thrush.ravenbrook.com> <20130903231205.1b713d11.reed@reedloden.com> Message-ID: <5226EC1C.2070808@mozilla.org> On 04/09/13 07:50, Michiel Beijen wrote: > Ah, that's great. I missed that part of the discussion, sorry! Hi Michiel, Don't let that deter you! Reed doesn't have time to drive that patch, so it would be wonderful if either you drove his patch to completion and checkin, or provided an alternative patch to implement the same function. I'm certainly keen to see this in Bugzilla. Gerv From michiel.beijen at gmail.com Wed Sep 4 08:18:46 2013 From: michiel.beijen at gmail.com (Michiel Beijen) Date: Wed, 4 Sep 2013 10:18:46 +0200 Subject: Password Hashes, Again In-Reply-To: <5226EC1C.2070808@mozilla.org> References: <38798.1334581659@thrush.ravenbrook.com> <20130903231205.1b713d11.reed@reedloden.com> <5226EC1C.2070808@mozilla.org> Message-ID: On Wed, Sep 4, 2013 at 10:15 AM, Gervase Markham wrote: > Don't let that deter you! Reed doesn't have time to drive that patch, so > it would be wonderful if either you drove his patch to completion and > checkin, or provided an alternative patch to implement the same > function. I'm certainly keen to see this in Bugzilla. So, I'm new to Bugzilla development, what would that take? From gerv at mozilla.org Wed Sep 4 08:31:22 2013 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 04 Sep 2013 09:31:22 +0100 Subject: Password Hashes, Again In-Reply-To: References: <38798.1334581659@thrush.ravenbrook.com> <20130903231205.1b713d11.reed@reedloden.com> <5226EC1C.2070808@mozilla.org> Message-ID: <5226EFDA.30905@mozilla.org> On 04/09/13 09:18, Michiel Beijen wrote: > So, I'm new to Bugzilla development, what would that take? Head over to bug https://bugzilla.mozilla.org/show_bug.cgi?id=672129 and have a look at Reed's patch. If you think "wow, he certainly did that well, it's better than my implementation" ( :-) ), then take it, replace yours, fix it as necessary, test it, and the reattach it. If you think "nice, but mine works just as well, and I'm more familiar with it" (possibly a more likely outcome), then attach your patch there with a description and request review from someone. Perhaps Reed would be willing to review it? :-) Gerv From fey at apiomat.com Thu Sep 5 04:36:19 2013 From: fey at apiomat.com (Andreas Fey) Date: Wed, 4 Sep 2013 21:36:19 -0700 (PDT) Subject: Creating aproduct on testing system Message-ID: <1e14e02a-3a70-4d43-a753-492719a2e174@googlegroups.com> Hi, we are currently trying to create a client to the Bugzilla REST API (https://wiki.mozilla.org/Bugzilla:REST_API). Basics are working fine, but i want to create a own product but cannot find a link on the user interface https://landfill.bugzilla.org/bzapi_sandbox to do this. Thanks, Andreas _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Thu Sep 5 09:03:11 2013 From: gerv at mozilla.org (Gervase Markham) Date: Thu, 05 Sep 2013 10:03:11 +0100 Subject: Creating aproduct on testing system In-Reply-To: <1e14e02a-3a70-4d43-a753-492719a2e174@googlegroups.com> References: <1e14e02a-3a70-4d43-a753-492719a2e174@googlegroups.com> Message-ID: On 05/09/13 05:36, Andreas Fey wrote: > we are currently trying to create a client to the Bugzilla REST API (https://wiki.mozilla.org/Bugzilla:REST_API). > Basics are working fine, but i want to create a own product but cannot find a link on the user interface https://landfill.bugzilla.org/bzapi_sandbox to do this. I have given your account "editcomponents" privileges on that installation, which should allow you to create a product to use for testing. Please, don't mess things up :-) Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gawol at apiomat.com Fri Sep 6 12:36:37 2013 From: gawol at apiomat.com (Gregor Gawol) Date: Fri, 6 Sep 2013 05:36:37 -0700 (PDT) Subject: update a bug entry on testing system Message-ID: <7bac425d-cde3-4761-8e10-26501262b14e@googlegroups.com> Hi, i want to update a bug on testing system. I do need a update_token. In Bugzilla Mozilla Wiki that i see the token when i'm logged. But I see nowhere a update_token. Can anyone tell me where to find him. Thanks, Gregor _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Tue Sep 10 10:18:39 2013 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 10 Sep 2013 11:18:39 +0100 Subject: update a bug entry on testing system In-Reply-To: <7bac425d-cde3-4761-8e10-26501262b14e@googlegroups.com> References: <7bac425d-cde3-4761-8e10-26501262b14e@googlegroups.com> Message-ID: <522EF1FF.2020402@mozilla.org> On 06/09/13 13:36, Gregor Gawol wrote: > i want to update a bug on testing system. Using which API? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gawol at apiomat.com Tue Sep 10 12:40:47 2013 From: gawol at apiomat.com (Gregor Gawol) Date: Tue, 10 Sep 2013 05:40:47 -0700 (PDT) Subject: update a bug entry on testing system In-Reply-To: <522EF1FF.2020402@mozilla.org> References: <7bac425d-cde3-4761-8e10-26501262b14e@googlegroups.com> <522EF1FF.2020402@mozilla.org> Message-ID: Am Dienstag, 10. September 2013 12:18:39 UTC+2 schrieb Gervase Markham: > On 06/09/13 13:36, Gregor Gawol wrote: > > > i want to update a bug on testing system. > > > > Using which API? > > > > Gerv i use latest. Gregor _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Tue Sep 10 13:19:46 2013 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 10 Sep 2013 14:19:46 +0100 Subject: update a bug entry on testing system In-Reply-To: References: <7bac425d-cde3-4761-8e10-26501262b14e@googlegroups.com> <522EF1FF.2020402@mozilla.org> Message-ID: <522F1C72.2010209@mozilla.org> On 10/09/13 13:40, Gregor Gawol wrote: > i use latest. This conversation needs to move to mozilla.support.bugzilla. Please can you repost your question there? Please include: * Which API you are using (native API, BzAPI, or whatever) * What exactly you did * What you expected to happen * What happened instead Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Tue Sep 10 17:03:34 2013 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Tue, 10 Sep 2013 13:03:34 -0400 Subject: Mozilla hiring another Bugzilla dev Message-ID: <522F50E6.9090109@mozilla.com> Hi, I'm the manager of the BMO (bugzilla.mozilla.org) team. I'm pleased to announce that we're hiring another developer to help out with both customizations to mee Mozillians needs and more generic features to drive Bugzilla further into the future. The full job posting is on our careers site: https://careers.mozilla.org/en-US/position/o99RXfwQ If you're interested, please apply directly or send me your resume. Mark From brian.wisti at gmail.com Thu Sep 12 21:58:11 2013 From: brian.wisti at gmail.com (Brian Wisti) Date: Thu, 12 Sep 2013 14:58:11 -0700 Subject: Self-Introduction: Brian Wisti Message-ID: Hi all, I have been looking at the Bugzilla code - partly because I saw a job posting, but also because I want to be more useful to the Free/Open Source Software world at large. That led me to https://wiki.mozilla.org/Bugzilla:Developers:Introduction - so I'm introducing myself. * Full legal name: Brian Wisti * Your IRC nick on irc.mozilla.org: Don't have one just yet. * City, Country: Seattle (Washington) USA * Profession or Student status: The titles vary, but the jobs have been mostly Web dev, and mostly Perl. * Company, School, or other affiliation: Currently working for McKesson, a medical technology company * What do you want to help out with? My plan was to start by going through the "Good Intro Bugs" and picking some particularly low-hanging fruit to familiarize with the process. Maybe "Move JS code out of bug/edit.html.tmpl" * Historical qualifications ** What other technical projects have you worked on in the past? I have not contributed significantly to any major open source projects. Since I do Perl so much at work, a lot of the free time play has been exploring other languages like Ruby, Python, and recently JavaScript. Oh - I did add Markdown formatting to posts in Diaspora , a feature which was widely loved and hated. So there's that. My major personal project at the moment is a Ruby on Rails floor management application for a local day shelter . It helps staff track client checkins, chores, incentive points, disciplinary flags, and whatever else is requested by staff members. Thanks to Twitter Bootstrap, I was able to develop the interface in such a way that it is useful on staff smartphones. Perl is still my most comfortable language, despite all that Ruby in the paragraph above. ** What level and type of computer skills do you have? I would describe myself as comfortable with FOSS development in general and Perl in particular. I've been living on Linux (or a full screen iTerm on OS X) for a while, writing Perl for pay for most of that time. ** What other skills do you have that might be applicable? User interface design, other so-called soft skills (people skills), etc. Definitely not a UX guy, though I have been able to fake it when working closely with my users. I can write tutorial material. Spent some time working on a Parrot PIR tutorial a few years back when I started exploring Perl 6, and those pages still get a little traffic . ** Anything else you'd like to say. Just hoping that this long and rambling email isn't overkill for saying "hey all, I would like to help out." Kind Regards, Brian Wisti http://randomgeekery.org From aaron.trevena at gmail.com Tue Sep 17 08:04:44 2013 From: aaron.trevena at gmail.com (Aaron Trevena) Date: Tue, 17 Sep 2013 09:04:44 +0100 Subject: Mozilla hiring another Bugzilla dev In-Reply-To: <522F50E6.9090109@mozilla.com> References: <522F50E6.9090109@mozilla.com> Message-ID: Hi Mark, Have you posted the job details at jobs.perl.org? A. From mcote at mozilla.com Tue Sep 17 14:40:33 2013 From: mcote at mozilla.com (=?ISO-8859-1?Q?Mark_C=F4t=E9?=) Date: Tue, 17 Sep 2013 10:40:33 -0400 Subject: Mozilla hiring another Bugzilla dev In-Reply-To: References: <522F50E6.9090109@mozilla.com> Message-ID: <523869E1.40706@mozilla.com> On 2013-09-17 4:04 AM, Aaron Trevena wrote: > Hi Mark, > > Have you posted the job details at jobs.perl.org? > I haven't! Will do. Thanks for the link. Mark From mi at ya.ru Wed Sep 18 21:17:44 2013 From: mi at ya.ru (Nikolay Mishin) Date: Thu, 19 Sep 2013 01:17:44 +0400 Subject: Self-Introduction: Nikolay Mishin In-Reply-To: <1461379538618@web28m.yandex.ru> Message-ID: <284071379539064@web1j.yandex.ru> An HTML attachment was scrubbed... URL: From mi at ya.ru Wed Sep 18 21:10:18 2013 From: mi at ya.ru (Nikolay Mishin) Date: Thu, 19 Sep 2013 01:10:18 +0400 Subject: Self-Introduction: Nikolay Mishin Message-ID: <1461379538618@web28m.yandex.ru> An HTML attachment was scrubbed... URL: