incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <robw...@apache.org>
Subject Re: Problems sign in consultants directory
Date Sun, 14 Oct 2012 16:09:52 GMT
On Sun, Oct 14, 2012 at 12:00 PM, Alexandro Colorado <jza@oooes.org> wrote:
> On 10/14/12, Rob Weir <robweir@apache.org> wrote:
>> On Sun, Oct 14, 2012 at 11:32 AM, Alexandro Colorado <jza@oooes.org> wrote:
>>> On 10/14/12, Rob Weir <robweir@apache.org> wrote:
>>>> On Sun, Oct 14, 2012 at 11:20 AM, Alexandro Colorado <jza@oooes.org>
>>>> wrote:
>>>>> Please write an example on the page, not just throw the XML file doing
>>>>> something as simple as
>>>>> <consultant>
>>>>> <company>Your company</company>
>>>>> <address>foo street at disneyland</address>
>>>>> <website>http://www.yourcompany.com</website>
>>>>> </consultant>
>>>>>
>>>>
>>>> There is an entire file of real examples linked to from that page:
>>>> https://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/content/bizdev/consultants/consultants.xml
>>>
>>> My point exactly. I would rather see this shown as HTML/ASCII, the XML
>>> dump is not bad but usually end up in  hard to read spew of data that
>>> non-technical users can't understand what happened.
>>>
>>>>
>>>>> Would go a long way, the instructions look a bit too technical for
>>>>> regular users. Even if we assume this are technical people, we should
>>>>> think this is being applied by the marketing intern used to facebook.
>>>>>
>>>>> I would even suggest doing an XForm to generate this XML and spew it
>>>>> on a texboard with a copy-paste this on your email.
>>>>>
>>>>
>>>> Patches are welcome.
>>>
>>> Here is an XForm sample:
>>> <xforms>
>>> <model>
>>> <instance>
>>>   <person>
>>>     <fname/>
>>>     <lname/>
>>>   </person>
>>> </instance>
>>> <submission id="form1"
>>> action="submit.asp"
>>> method="get"/>
>>> </model>
>>> <input ref="fname"><label>First Name</label></input>
>>> <input ref="lname"><label>Last Name</label></input>
>>> <submit submission="form1"><label>Submit</label></submit>
>>> </xforms>
>>>
>>
>> The form is the easy part.  The hard part is getting it integrated in
>> a way that works with our current server environment.  As you've
>> probably noticed we don't have mail-in forms anywhere on our website.
>> Perhaps there are some security issues here?  Infra would know.  But
>> there would be some work to either enable the server-side processing
>> of this, or of generating the XML with instructions for the user to
>> copy/paste it into an email to ooo-dev.
>>
>> Personally I don't think the expected volume of submissions justifies
>> the time required to put further automation into play.  (My personal
>> opinion).  As the instructions say, the submittor can just send
>> equivalent information to the list and we can do the XML formatting
>> for them.
>
> Ok the original proposal was that it will dump the data in a texbox
> (Javascript can do this as opposed to the submit.asp). Just to
> pre-format his entry, user  can then paste it on an email.
>
> And if no automation is necessary then I think it should be the first
> thing said, like this:
>
> Please submit the information to our ooo-dev mailing list:
>
> - Company name
> - Country code [1]
> - Address
> - URL
> -Specialities: [2]
>
> 1 - see our ISO compliant country listing
> 2 - see our list of specialties
>
> The rest of the information like XML, XSD, etc, should be put as
> complementary information.
>

This is a good idea.  I'll try to simplify the instructions.

-Rob

>
>>
>> -Rob
>>
>>>>
>>>>> Specially consider the speciality would be all over the place as a
>>>>> freeform XML.
>>>>>
>>>>
>>>> In the current form it is restricted to enumerated values.  This list
>>>
>>> Oh there is a form, I most have missed that.
>>>
>>>> can expand on request, but I'd like to not have it be freeform so it
>>>> can be used as a categorization field.  The <description> field is
the
>>>> freeform field, where they can put anything relevant.
>>>>
>>>>> On 10/14/12, Rob Weir <robweir@apache.org> wrote:
>>>>>> On Sun, Oct 14, 2012 at 10:27 AM, Jörg Schmidt <joesch@j-m-schmidt.de>
>>>>>> wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> I now have sent an invitation to 41 companies relating to an
entry in
>>>>>>> the
>>>>>>> directory:
>>>>>>> http://www.openoffice.org/bizdev/consultants.html
>>>>>>>
>>>>>>> And I got the first reply:
>>>>>>>
>>>>>>> ----------------
>>>>>>>> Listings must be submitted to the ooo-dev mailing list as
patches to
>>>>>>>> the
>>>>>>>> file consultants.xml
>>>>>>>  >
>>>>>>>
>>>>>>> nicht Ihr Ernst, oder?
>>>>>>> ----------------
>>>>>>>
>>>>>>> No problem in this individual case, because I offered my personal
>>>>>>> help,
>>>>>>> but I think it may seem too complicated for some users even having
to
>>>>>>> create an XML file.
>>>>>>>
>>>>>>> What can we do?
>>>>>>>
>>>>>>> For example, i could write a macro for AOO with an input dialog,
>>>>>>> which
>>>>>>> simplifies the creation of the XML file. But I need a few days
time.
>>>>>>>
>>>>>>> Hints?
>>>>>>>
>>>>>>
>>>>>> This is covered in the instructions here:
>>>>>>
>>>>>> "If you are not familiar with XML, please submit the equivalent
>>>>>> information in a post to the ooo-dev list and we can help you format
>>>>>> it for submission. But your listing will appear faster if it is
>>>>>> submitted in the proper form."
>>>>>>
>>>>>> Reference:
>>>>>> http://www.openoffice.org/bizdev/consultant-submission.html
>>>>>>
>>>>>> A form with Javascript to form the XML might be useful sometime,
but
>>>>>> it is possible that the XML schema might change based on feedback
we
>>>>>> receive during this initial phase of submissions.  So it might be
>>>>>> better to wait.
>>>>>>
>>>>>> -Rob
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Greetings,
>>>>>>> Jörg
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Alexandro Colorado
>>>>> PPMC Apache OpenOffice
>>>>> http://es.openoffice.org
>>>>
>>>
>>>
>>> --
>>> Alexandro Colorado
>>> PPMC Apache OpenOffice
>>> http://es.openoffice.org
>>
>
>
> --
> Alexandro Colorado
> PPMC Apache OpenOffice
> http://es.openoffice.org

Mime
View raw message