Talk:OpenDroneMap
So far so good, this project looks like free software. However, we are working on creating a project page template for the FSD because each the five repos <https://github.com/OpenDroneMap> should have their own entries because there is currently not an effective way to group entries under a single unified project. —craigt (contribs) 15:20, 15 April 2022 (EDT)
- Thanks, craigt. I'm curious, though, why not approve the edit and let the page be seen while you continue your work on the template tooling? I'm sure you agree that the raison d'être for a wiki is to allow information to evolve, and it seems to me that what I assembled here can only begin to do that once it's presented to users along with the rest of what's here. At the very least, it'd be a friendly overture toward a new contributor from which you could then invite me to take a look at what you've got so far on your project page template, where I'd quite likely be inclined to apply whatever skill 19 years of template use and design at the Wikimedia projects has afforded me in the service of your project. ;) —RogueScholar (talk|contribs) 22:31, 27 June 2022 (EDT)
- @craigt, how goes the templating work? I'd like to contribute here more but, as I'm sure you can understand, there's a strong disincentive to do so when your efforts are stuck in (seemingly) perpetual limbo. —RogueScholar (talk|contribs) 00:03, 26 April 2023 (EDT)
- @RogueScholarYou're right. I will prioritize my work for this. Craigt (talk) 15:01, 5 May 2023 (EDT)
- @RogueScholarThanks for the encouragement. I was able to approve OpenDroneMap. However, I was having trouble with identifying the copyright holders of OpenDroneMap. Is there anything you can share with me about the copyright status of OpenDroneMap? Craigt (talk) 15:00, 26 May 2023 (EDT)
- @craigt, this is great! I just now logged in and saw it for the first time. Regarding the copyright holders, since it's developed using version control (Git) I would conclude that they would collectively be those listed here. All development has occurred within the last 15 years so the implicit copyright granted to creative works must assuredly still be in effect. Am I missing something? I think I might be misunderstanding your question. Thanks again. —RogueScholar (talk|contribs) 05:59, 30 July 2023 (EDT)
- That link will work. Thanks. It doesn't look like OpenDroneMap is concerned about its copyright status of the overall project. Which is fine I suppose, but it would make enforcing the AGPLv3 difficult (if not impossible). They do have a trademark they protect though. Craigt (talk) 13:28, 4 August 2023 (EDT)
- @craigt: Haha, based on my own anecdotal experience, I believe you're quite correct and very possibly understating the matter by quite a bit. In casual conversation with a couple different contributors I attempted to gain some clarity into their approach to rights assignment and licensing and the swift response on both occasions could be succinctly paraphrased as
"Coders code, and only sleazy businessmen worry about the names on the credits panel and which license file is in the repo."
- @craigt: Haha, based on my own anecdotal experience, I believe you're quite correct and very possibly understating the matter by quite a bit. In casual conversation with a couple different contributors I attempted to gain some clarity into their approach to rights assignment and licensing and the swift response on both occasions could be succinctly paraphrased as
- That link will work. Thanks. It doesn't look like OpenDroneMap is concerned about its copyright status of the overall project. Which is fine I suppose, but it would make enforcing the AGPLv3 difficult (if not impossible). They do have a trademark they protect though. Craigt (talk) 13:28, 4 August 2023 (EDT)
- @craigt, this is great! I just now logged in and saw it for the first time. Regarding the copyright holders, since it's developed using version control (Git) I would conclude that they would collectively be those listed here. All development has occurred within the last 15 years so the implicit copyright granted to creative works must assuredly still be in effect. Am I missing something? I think I might be misunderstanding your question. Thanks again. —RogueScholar (talk|contribs) 05:59, 30 July 2023 (EDT)
- @RogueScholarThanks for the encouragement. I was able to approve OpenDroneMap. However, I was having trouble with identifying the copyright holders of OpenDroneMap. Is there anything you can share with me about the copyright status of OpenDroneMap? Craigt (talk) 15:00, 26 May 2023 (EDT)
- @RogueScholarYou're right. I will prioritize my work for this. Craigt (talk) 15:01, 5 May 2023 (EDT)
- @craigt, how goes the templating work? I'd like to contribute here more but, as I'm sure you can understand, there's a strong disincentive to do so when your efforts are stuck in (seemingly) perpetual limbo. —RogueScholar (talk|contribs) 00:03, 26 April 2023 (EDT)
- Honestly, I'm sympathetic to that position myself, but as someone who's often straddled the line between software and business and borne witness to the unkind treatment that often befalls those who willfully ignore those unpleasant realities, I do my best to avoid that fate when possible. Your observations are right on the money and the whole approach has a slapdash feel to it, but for my part I generally avoid getting bogged down in minutiae, especially when it belongs to others. Thanks again for shepherding this entry into the directory and keep me in mind if you ever want to collaborate on workflow tools and the like for this place. Warmly, —RogueScholar (talk|contribs) 18:45, 12 August 2023 (EDT)
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.