Send Motion-user mailing list submissions to
motion-user@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
motion-user-requ...@lists.sourceforge.net
You can reach the person managing the list at
motion-user-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: [Motion-devel] Motion Project (Kenneth Lavrsen)
2. Re: [Motion-devel] Motion Project (John Baker)
3. Re: [Motion-devel] Motion Project (Kenneth Lavrsen)
----------------------------------------------------------------------
Message: 1
Date: Fri, 5 Aug 2016 20:52:52 +0200
From: Kenneth Lavrsen <kenn...@lavrsen.dk>
Subject: Re: [Motion-user] [Motion-devel] Motion Project
To: Motion discussion list <motion-user@lists.sourceforge.net>
Cc: Motion SVN commit messages <motion-de...@lists.sourceforge.net>
Message-ID: <1642eeb4-03a1-44ac-a568-179075067...@lavrsen.dk>
Content-Type: text/plain; charset="us-ascii"
Tosiara
I do not understand your sharp tone.
I have agreed to pass over the project.
And I wrote below I am OK that bug reports etc are moving to Github.
But you also have to be honest here
You guys have added several new options and new values to existing options. And
none of you could be bothered to update the documentation. I just read 2-3
questions on this mailing list that relates to options that are not documented.
It takes days to code a new feature and test it. It takes 10 minutes to
document it. I can for the world not understand why programmers in general do
not understand the importance of documenting how it works.
Bugs report, feature requests will be removed from the wiki. Patches work so
much better with pull requests on git. I will remove all this also.
It is the Motion Guide that I will like see online and up to date. I will be
happy to bring it up to date provided that you tell me how the new things work.
Last time I tried to build Motion I found several features that I do not know
how to use!!!
Tell me how it works and I will update the docus. And I also commit to remove
all the abandonned features on the wiki. I do not have time to code and develop
Motion but As I said I am OK to keep the wiki running and the Motion Guide
working. But I need you guys to commit (gentlemens agreement) that you will
keep the documentation up to date (with my help with the practical stuff) and
also make sure the man pages and the html version of the Motion guide up to
date. As I said it is easy. When the wiki docu is up to date it will
autogenerate the html and manpage.
You guys focus on the code and supporting the users. I keep the wiki alive and
update the docu which is probably 20-30 minutes work per year. I use the wiki
for other things so keeping it alive is not an issue. And if you guys feed me
when you add new features or edit the existing pages when you change the
existing options then it is not a problem for me. And when I hand over the
project I also hand over all decisions on what is changed. I just become the
project secretary and wiki admin.
So MrDave, Joerg Weber, Tosiara. Are you game to become the official new Motion
team with MrDave as the new formal owner?
And anyone else wanting to commit to help along?
Kenneth
> On 05 Aug 2016, at 09:48, tosiara <tosi...@gmail.com> wrote:
>
> Kenneth,
>
> Let's be honest, SVN version is dead. Poor RTSP support, configure and build
> issues, deprecated ffmpeg functions and lots of bugs (including security
> issues with buffer overflow which can allow remote code execution). A lot of
> people already switched to MrDave's fork and all of them seem to be happy
> with existing documentation.
>
> Fowsiki contains a lot of info, right. But it is still quite outdated and
> nobody maintains it. For example, how many support requests have been
> resolved recently? Check it out:
> http://www.lavrsen.dk/foswiki/bin/view/Motion/SupportRequests I tried to do
> my best to provide users support through Foswiki, but the nature of wiki
> engine is so, that users never get notifications about answers and don't
> provide further details. No bug tracking at all. Patch submission is so hard,
> that nobody uses that. How many patches have been received and merged for the
> past few years? Zero.
>
> Just take a look how the life goes on at github:
> https://github.com/Mr-Dave/motion/issues?q=is%3Aissue+is%3Aclosed
> People submit patches and their changes get merged into master branch. Not as
> fast as it could be (as only MrDave maintains the repo), but at least they
> exist. You can see on the fork map how many people are keeping coding and
> even updating README: https://github.com/Mr-Dave/motion/network
>
> This motion version is alive and is evolving.
> All we need is to give it the official status so all the distros pulls this
> new version, because it is de facto "real" motion. Everyone will benefit
>
>> On Fri, Aug 5, 2016 at 5:49 AM, Kenneth Lavrsen <kenn...@lavrsen.dk> wrote:
>> Resent to the right mailing list
>>
>> Mr Dave
>>
>> I am happy to to see the project handed over to someone that will give it
>> tender love and care. I had hoped to get time for it again but I have to
>> recognize that I do not even have time to read this mailing list
>>
>> I can see from this thread that there is a team willing to take over and
>> that is good.
>>
>> The only concern I have is documentation.
>>
>> When I joined the Motion project, it was wonderful code with no
>> documentation at all. And very few users because noone had a clue how to use
>> the code.
>>
>> I changed that and wrote the Motion Guide. It changed the project
>> completely. A year later the project was given to another coder while I
>> maintained the documentation. And finally I took over the project but I was
>> never the main coder.
>>
>> I created this mailing list. I moved the project on to Twiki and later to
>> Foswiki which I participated in very actively.
>>
>> To pass on the project is easy. To find people willing to do the work is the
>> difficult part.
>>
>> The team that takes over need to do more than just code. You need to keep a
>> project like Motion fully documented. A config file based program does not
>> explain itself the way a GUI program does. The config file itself is not
>> enough.
>>
>> I would like some commitment that you guys will not just code and code and
>> code but also ensure that Motion is still a well documented project.
>>
>> Moving the code to Git. Moving the bug reporting away from the current wiki.
>> Fine! Feature requests etc etc. No worries.
>>
>> I will be happy to continue running the server and the Foswiki. The Motion
>> Guide part of the wiki is actually very smart and it requires very little
>> work to maintain the documentation if you invest an hour learning how it
>> works. The documentation builds itself. It will even build the manpage for
>> you. All it requires is maintaining one simple "database" record on the wiki
>> per config parameter. And it is a good idea that it is not the coders that
>> maintain this as long as they pass on the information.
>>
>> It is hard to run a project on your own. It needs a leader that can take the
>> final decisions and formally owns it. I am no longer the right person for
>> that, because of lack of time. I am OK to pass on the ownership. But it
>> would be nice if I knew that there are 3-4 of you willing to help. And I am
>> deeply concerned about the project falling back to undocumented geek mode
>> where only C programmers that can read the code can use the software. That
>> would be very sad.
>>
>> I will make an effort on reading the mailing list the next days
>>
>> Kenneth
>>
>> > On 05 Aug 2016, at 02:29, Mr Dave <motionmrd...@gmail.com> wrote:
>> >
>> > Kenneth,
>> >
>> > I believe it is a best practice to formally ask you to take over the
>> > Motion project before I officially move to create a new project. Please
>> > let me know either way of your decision. If you are uncomfortable passing
>> > it to me, would you consider putting it up for adoption to someone else
>> > that would be able to maintain it.
>> >
>> > MrDave
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Motion-devel mailing list
>> motion-de...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/motion-devel
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Fri, 05 Aug 2016 20:00:38 +0100
From: John Baker <jba...@dryfish.org.uk>
Subject: Re: [Motion-user] [Motion-devel] Motion Project
To: motion-user@lists.sourceforge.net
Message-ID:
<1470423638.3361453.687238657.3b367...@webmail.messagingengine.com>
Content-Type: text/plain
If someone wants to re-write the core modules in Python, I'd pitch in
with an AngularjS UI & Flask REST support.
------------------------------
Message: 3
Date: Fri, 5 Aug 2016 21:25:08 +0200
From: Kenneth Lavrsen <kenn...@lavrsen.dk>
Subject: Re: [Motion-user] [Motion-devel] Motion Project
To: Motion discussion list <motion-user@lists.sourceforge.net>
Message-ID: <8bc03015-792b-4a1a-aa18-e1ad6d5b0...@lavrsen.dk>
Content-Type: text/plain; charset=us-ascii
John Baker
I do not know you but I can see you are very active here. That makes me even
more happy to hand over the project. Keep on the good work
Kenneth
> On 05 Aug 2016, at 21:00, John Baker <jba...@dryfish.org.uk> wrote:
>
> If someone wants to re-write the core modules in Python, I'd pitch in
> with an AngularjS UI & Flask REST support.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
------------------------------
------------------------------------------------------------------------------
------------------------------
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 123, Issue 4
*******************************************
