students participating in OOo

[Cem Kaner <ka...@kaner.com>]

I just noticed a request for professors to let you know when their students
are joining the OOo projects.

 

I teach courses in software testing at Florida Tech (Florida Tech students)
and through Kaner/Fiedler Associates (you'll see students from companies
coming through us, such as, currently, Progressive Insurance). One of each
of these classes is actively working with OOo right now.

 

These are the BBST courses, which the Association for Software Testing and
Arizona State also teach. Other places teach them too, but those are the
groups that I know currently follow my suggestion to work on OpenOffice.

 

Students in these classes review two unconfirmed bugs each, posting comments
on the OOo database that are intended to help you confirm or reject a bug.
They also write evaluations of the communication quality of the bug reports,
which our class sees but your bug reporters don't see (some of the
evaluations are unflattering; there is no value in insulting volunteers by
publicly critiquing their reports).

 

If you're curious, I can send you a copy of the assignment. I generally
teach two university courses and 2-3 corporate courses per year. ASU
teaches, I think, two courses. 

 

If you wanted to encourage this, the best support you could give us would be
to confirm or reject bugs quickly after we studied them, or to post comments
on the bug that followed up on our notes (e.g. asked additional questions).
If you are happy to give this kind of fast feedback, I could send you a list
of the volunteers on your project who are willing to be identified to you as
our students (privacy laws require me to get their permission).

 

Cordially

 

Cem Kaner, JD., Ph.D.

www.kaner.com

Professor of Software Engineering, Florida Tech

 

Re: students participating in OOo

[Andrea Pescetti <pe...@apache.org>]

Alexandro Colorado wrote:
>> I teach courses in software testing at Florida Tech (Florida Tech students)
>> and through Kaner/Fiedler Associates (you'll see students from companies
>> coming through us, such as, currently, Progressive Insurance). One of each
>> of these classes is actively working with OOo right now.
> ​That's great news.​ We could write an article on our blog as a case study
> in the future.

Indeed, it is very helpful to know about this. And Cem, please do turn 
this information into a blog post that we can publish at 
http://blogs.apache.org/OOo/ (or, if it's easier for you, you can post 
an article on a personal blog and then we can mirror it on the official 
Apache OpenOffice blog).

>> If you're curious, I can send you a copy of the assignment.

Please do! Attachments will not make it to the list, but text in a 
normal e-mail will be enough.

>> If you are happy to give this kind of fast feedback, I could send you a
>> list
>> of the volunteers on your project who are willing to be identified to you
>> as our students (privacy laws require me to get their permission).
>
> ​It would be more of use, if the students themselves come forward either on
> this list, or the QA one to talk about the current reports.​

Exactly. It's best that they join the QA mailing list 
http://openoffice.apache.org/mailing-lists.html and introduce 
themselves. We will grant them extended permissions in Bugzilla if they 
can benefit from this, we'll guide them and keep an eye on the bugs they 
analyze, provided that they keep the QA list informed about their 
Bugzilla activity.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: students participating in OOo

[Alexandro Colorado <jz...@oooes.org>]

Hello,  comments inline:


On Thu, Sep 19, 2013 at 12:29 AM, Cem Kaner <ka...@kaner.com> wrote:

> I just noticed a request for professors to let you know when their students
> are joining the OOo projects.
>
>
>
> I teach courses in software testing at Florida Tech (Florida Tech students)
> and through Kaner/Fiedler Associates (you'll see students from companies
> coming through us, such as, currently, Progressive Insurance). One of each
> of these classes is actively working with OOo right now.
>

​That's great news.​ We could write an article on our blog as a case study
in the future.

These are the BBST courses, which the Association for Software Testing and
> Arizona State also teach. Other places teach them too, but those are the
> groups that I know currently follow my suggestion to work on OpenOffice.
>
>
>
> Students in these classes review two unconfirmed bugs each, posting
> comments
> on the OOo database that are intended to help you confirm or reject a bug.
>

​Are you talking about bugzilla @ https://issues.apache.org/ooo/ ?​



> They also write evaluations of the communication quality of the bug
> reports,
> which our class sees but your bug reporters don't see (some of the
> evaluations are unflattering; there is no value in insulting volunteers by
> publicly critiquing their reports).
>

​We have a Quality Assurance mailing list, this will insure the bugs  get
at least the right amount of attention.​

​However is important these bugs are correctly documented, please check out
these instructions on how to write a bug:
http://wiki.openoffice.org/wiki/QA/HowToFileIssue​


If you're curious, I can send you a copy of the assignment. I generally
> teach two university courses and 2-3 corporate courses per year. ASU
> teaches, I think, two courses.
>

​It would be more helpful to have the bug report # so we can review them on
the list.


> If you wanted to encourage this, the best support you could give us would
> be
> to confirm or reject bugs quickly after we studied them, or to post
> comments
> on the bug that followed up on our notes (e.g. asked additional questions).
>

​Unfortunately we don't have the resources to confirm all the bugs that get
generated by users or testers. You are welcome however to become a tester
or a developer and submit the patches required. You can bring questions
regarding the coding convention and the possible development solutions with
the other developers and test the new patch on our nightly builds.



> If you are happy to give this kind of fast feedback, I could send you a
> list
> of the volunteers on your project who are willing to be identified to you
> as
> our students (privacy laws require me to get their permission).
>

​It would be more of use, if the students themselves come forward either on
this list, or the QA one to talk about the current reports.​



>
>
>
> Cordially
>
>
>
> Cem Kaner, JD., Ph.D.
>
> www.kaner.com
>
> Professor of Software Engineering, Florida Tech
>
>
>
>


-- 
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org