[Libre-soc-dev] I'm about to create 54 bug reports for diagrams

[Cole Poirier]

On Tue, Aug 4, 2020 at 11:53 AM Luke Kenneth Casson Leighton
<lkcl at lkcl.net> wrote:
>
> On Tue, Aug 4, 2020 at 7:27 PM Cole Poirier <colepoirier at gmail.com> wrote:
> >
> > How do I set up my access to the ftp server for the purpose of this task?
>
> you don't: i do.  from the account that has this ssh key ("deb at debian"):
>
> $ sftp ftp at libre-soc.org
> Connected to libre-soc.org.
> sftp> ls
>
> however i just realised something: strictly speaking we do not even
> need to quotes upload quotes any images at all.
>
> we're thinking about this in the wrong way, because of the practice of
> following quotes graphical drawing practices quotes.
>
> we are software engineers.  graphical design artists are, well...
> ignorant of software engineering practices.  they therefore created
> the "workflow" of having dozens of copies of the exact same file,
> multiple times, with minimal variations.
>
> this is utterly wasteful yet because graphical design artists are
> ignorant of things like "git", it's all that they know and it quotes
> works for them quotes.
>
> (i've seen my mum take multiple copies of HUNDRED MEGABYTE raw image
> files for example).
>
>
> 1) we are using git (for both the wiki and the source code)
>
> 2) svg files are text-based.
>
> 3) therefore, they can go into git, they can be "diff"ed, and more.
>
> so.  i propose this:
>
>
> 1) for each new image: start (new) SVG images *in* the wiki git
> repository (without destroying or replacing the old one)
>
> 2) do NOT create D1, D2, D3, F1, F2 versions of the images, copied OUT
> of the wiki and into some random arbitrary "image editing directory".
>
> 3) run inkscape *IN PLACE* from the checked out location *in the git
> repository*.
>
> 4) after each modification, commit the change *to the wiki git
> repository*.  do NOT change its name.
>
> 5) do NOT upload the exact same image to the bugtracker as a file
> attachment.  DEFINITELY do not add a PNG version of that exact same
> image to the bugtracker.  drop the *URL* of the SVG image into a
> *comment* in the bugtracker when requesting a review.
>
> 6) when the image is finally approved, simply edit the wiki page to
> point to the SVG instead of the old JPEG hand-edited one.
>
>
> that's it.  nothing else needed.  basically we apply *software
> engineering* techinques to the management of these "text files that
> happen to have an SVG file extension"
>
> thoughts?

Yes, that sounds like a much better approach *however* jpgs of
the diagrams from Mitch's book chapters will have to be uploaded
because these are the 'originals' and are not in svg.

This will be 25(?) jpgs.

Thoughts?

Cole