Re: Derby Logo, Take Two [managing logo submissions]
Andrew Kachalo uploaded his logo (thanks, Andrew!) and an advantage I immediately see is that Jira itself displays the images. I have karma to manage attachments so can verify exactly who uploaded what, but not everyone can see that, so I'll add an index for the images. -jean Jean T. Anderson wrote: I opened DERBY-297 to handle logo submissions: http://issues.apache.org/jira/browse/DERBY-297 So, anyone can upload a logo to this Jira issue. You do need a Jira id, which you can sign up for here: http://issues.apache.org/jira/ If anyone has trouble signing up for a Jira id or uploading your submission, please post and we'll help you out. -jean
Re: Derby Logo, Take Two [managing logo submissions]
I opened DERBY-297 to handle logo submissions: http://issues.apache.org/jira/browse/DERBY-297 So, anyone can upload a logo to this Jira issue. You do need a Jira id, which you can sign up for here: http://issues.apache.org/jira/ If anyone has trouble signing up for a Jira id or uploading your submission, please post and we'll help you out. -jean Jean T. Anderson wrote: Craig Russell wrote: Taking this one step further, could we use Jira to tally votes? That would reduce the ambiguity over who is qualified to vote, and provide for one vote per Jira account... Just thinking(?) out loud. Yeah, I was thinking along the same lines and looked into it a little -- there's one vote for DERBY-257. :-) Voting seems to be a straight toggle in Jira (not multiple choice): either you vote for fixing the issue or not fixing the issue. I thought perhaps a subtask might be used for each logo entry. DERBY-167 has subtask DERBY-275. I voted for DERBY-275 just now, but that vote doesn't get reflected at the parent level. So we may still need a manual email tally unless somebody more Jira savvy has ideas. -jean
Re: Derby Logo, Take Two [managing logo submissions]
Craig Russell wrote: Taking this one step further, could we use Jira to tally votes? That would reduce the ambiguity over who is qualified to vote, and provide for one vote per Jira account... Just thinking(?) out loud. Yeah, I was thinking along the same lines and looked into it a little -- there's one vote for DERBY-257. :-) Voting seems to be a straight toggle in Jira (not multiple choice): either you vote for fixing the issue or not fixing the issue. I thought perhaps a subtask might be used for each logo entry. DERBY-167 has subtask DERBY-275. I voted for DERBY-275 just now, but that vote doesn't get reflected at the parent level. So we may still need a manual email tally unless somebody more Jira savvy has ideas. -jean
Re: Derby Logo, Take Two [managing logo submissions]
Taking this one step further, could we use Jira to tally votes? That would reduce the ambiguity over who is qualified to vote, and provide for one vote per Jira account... Just thinking(?) out loud. Craig On May 12, 2005, at 1:47 AM, Craig Russell wrote: Hi Jean, +1 to both. Requiring a logo submitter to get a Jira id sounds like a reasonable idea, and granting a license to use the logo at the time of upload makes perfect sense to me. Craig On May 11, 2005, at 1:37 PM, Jean T. Anderson wrote: In http://mail-archives.apache.org/mod_mbox/db-derby-user/200505.mbox/ [EMAIL PROTECTED] Susan Cline kick started the logo contest. She included this question: How will submissions be handled? Would anybody object to attaching logo submissions to a Jira issue (which I'll volunteer to open)? Managing submissions in Jira has the following advantages: 1) Uploading the file presents the opportunity to click on the button to "Grant license to ASF for inclusion in ASF works". 2) Organizing all submissions within a single Jira issue will make it easier to include on the web site for review (rather than searching through old list posts). Jira has the disadvantage that it requires an additional step to request a Jira id at http://issues.apache.org/jira/; however, anyone may request an id. thoughts? comments? agreement? disagreement? -jean Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
Re: Derby Logo, Take Two [managing logo submissions]
Hi Jean, +1 to both. Requiring a logo submitter to get a Jira id sounds like a reasonable idea, and granting a license to use the logo at the time of upload makes perfect sense to me. Craig On May 11, 2005, at 1:37 PM, Jean T. Anderson wrote: In http://mail-archives.apache.org/mod_mbox/db-derby-user/200505.mbox/ [EMAIL PROTECTED] Susan Cline kick started the logo contest. She included this question: How will submissions be handled? Would anybody object to attaching logo submissions to a Jira issue (which I'll volunteer to open)? Managing submissions in Jira has the following advantages: 1) Uploading the file presents the opportunity to click on the button to "Grant license to ASF for inclusion in ASF works". 2) Organizing all submissions within a single Jira issue will make it easier to include on the web site for review (rather than searching through old list posts). Jira has the disadvantage that it requires an additional step to request a Jira id at http://issues.apache.org/jira/; however, anyone may request an id. thoughts? comments? agreement? disagreement? -jean Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
Re: Derby Logo, Take Two [managing logo submissions]
In http://mail-archives.apache.org/mod_mbox/db-derby-user/200505.mbox/[EMAIL PROTECTED] Susan Cline kick started the logo contest. She included this question: How will submissions be handled? Would anybody object to attaching logo submissions to a Jira issue (which I'll volunteer to open)? Managing submissions in Jira has the following advantages: 1) Uploading the file presents the opportunity to click on the button to "Grant license to ASF for inclusion in ASF works". 2) Organizing all submissions within a single Jira issue will make it easier to include on the web site for review (rather than searching through old list posts). Jira has the disadvantage that it requires an additional step to request a Jira id at http://issues.apache.org/jira/; however, anyone may request an id. thoughts? comments? agreement? disagreement? -jean
