On 2013-08-19 22:25, Jo wrote:
Okay, then I looked at the wrong page, apparently. It all started as a
series of 'mechanical' operations on the data, but before submitting
some human intelligence still needs to be applied to make it all fit
with the existing data.
We can, of course, create an account like UrbisImport and then share
the password of that account. On the one hand that would seem quite
odd to me. On the other hand it kills the possibility to create
statistics on who does what where.
I guess I'm going to have to go and ask on talk-fr if they finally
gave in to the pressure from above and all created separate accounts
for integrating their cadastre. I don't think they actually did so and
I've always been saying that it shouldn't be necessary, just like they
have.
Unfortunately it's hard to agree to disagree on this sort of subject.
I may also take a sabbatical leave of a few years/decades from the
project. Just like I did when the talk about the license change
started. Unfortunately that went on for years. I hate these kind of
struggles.
Sharing passwords is a really bad move. First of all, there is no way
in a collaborative situation to figure out which _real_ person was
responsible for whatever fuckup may happen (I can assure you they _will_
happen).
I think professionals should refrain from suggesting procedures that
encourage this bad practise. I'm not even going to go deeper in the
'why' that -bluntly stated- is idiotic and sucks terribly. I don't
even see the merit in using a seperate single account for this. Maybe
it's the word 'import' that triggers this, but as far as I know the
Urbis work is not fully automated at all but it is reviewed by
motivated, hard working individuals to ensure quality.
So it's not an import in the pure sense as this seems to be
misunderstood by looking at the complaints.
There is actually a solutions for both problems, whatever constraints
are being forced upon those people that do the hard work. I guess they
are TOO motivated, situations such as these make you loose contributers
by the dozen. I for one am very concerned that Jo makes these
sabatical statements as one of the key players in the .BE OSM scene.
(just face it Jo, you are one of the driving forces, no denying it).
The solution is as simple as it gets:
Use a dedicated changeset tag, whatever account you use. being it
individuals or a dedicated account, put a well chosen changeset tag(s),
this can contain:
- the userID that made the effort, even though it's commited through
another account.
- the sort of import the changeset represents.
I think we already do the second one, since this is the way this got
spotted in the first place afaik. The first one we just need to aggree
upon as .BE OSM community.
Would love to hear what benefit a seperate/dedicated yet shared account
brings to the table. Take all the time you need to answer this.
Glenn
_______________________________________________
Talk-be mailing list
Talk-be@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-be
