7:26 a.m.
Hi Developers,
I'm going to try and be as verbose as possible about the procedure to
upload your own release to inkscape.org, I need you to perform this task
if you package any of our release packages because a) it's good practice
and b) packages will be signed with your gpg key and it'd be an odd
world where I could do that for you. :-)
Releasing on inkscape.org:
1. Make sure you have a user account on inkscape.org
- Go to https://inkscape.org and look in the top right of the page and
note your logged in status, use the links provided in the drop down to
log in or register an account.
2. Make sure that your account has a big enough quota
- Go to https://inkscape.org/user/ and hover over the "Upload Quota"
bar, you will only see 10MB if you are a normal user at this time. If
you do not see a 1GB quota then you need to contact a website admin (me)
to put you into the releases group with the larger quota.
3. Make sure you have a public gpg key recorded.
- Go to https://inkscape.org/user/edit/ and fill in the right boxes,
the GPG Public Key box is expecting a pasted public key (not private
key!) and hit submit when done.
4. Make a folder for your releases in your 'InkSpace'.
- Go to https://inkscape.org/gallery/new/ and fill in the name of the
folder you want to use. This folder is only for your own organisation
and won't be seen by users.
5. Upload your released file
- Go to https://inkscape.org/user/ and drag your file to the new
gallery folder created above. The upload may take some time but you
should be able to see a progress bar as it uploads. (if you don't have
javascript enabled, you can click on the folder and then click add and
follow the manual form)
6. Enter all the details
- Go into your folder and click on the newly uploaded item. It should
have a red border indicating it's not yet published (if you used the
drag+drop method)
- Going into the editor section you should be able to fill in the
title for the released file.
- Paste in the release notes into the description.
- Select 'Releases' from the category drop down.
- Attach the sig file from your detached.
- Select 'GPLv2' from the Licenses drop down.
- Check 'Mirror' checkbox (if you have this)
- Check 'Visible' checkbox
Submit this form.
7. Verify and copy link
- If everything's gone well you should now see your released file with
a green padlock indicating the gpg signature has been verified against
your account public key.
- Download the release by clicking on the down-arrow icon. Confirm
it's the file you intended.
- Copy this download link.
8. Link from the downloads page.
- For this step you will need CMS editor access or pass this task onto
a website editor and/or translator.
- Edit the downloads pages for the right OS and update with the right
version, release and other details as you would want it to be presented
to users. Add the copied link into the right place.
- Save /and/ then hit the blue publish button.
Congratulations, you've uploaded, released and published your release
file. Let the website administrator (me) know if you have any difficulty
with this process.
Best Regards, Martin Owens
6:24 p.m.
On Wed, Dec 31, 2014 at 05:26:20PM -0500, Martin Owens wrote:
Hi Developers,
I'm going to try and be as verbose as possible about the procedure to
upload your own release to inkscape.org, I need you to perform this task
if you package any of our release packages because a) it's good practice
and b) packages will be signed with your gpg key and it'd be an odd
world where I could do that for you. :-)
Releasing on inkscape.org:
1. Make sure you have a user account on inkscape.org
- Go to https://inkscape.org and look in the top right of the page and
note your logged in status, use the links provided in the drop down to
log in or register an account.
I attempted to log in this way, but got an error,
Forbidden (403)
CSRF verification failed. Request aborted.
More information is available with DEBUG=True.
Tried several times, no dice. Then went to
https://inkscape.org/user/edit, and got a different (full page) login
screen. Entered the same credentials, and it let me in just fine.
I logged out with the top right login manager, then used it again to log
in and this time it let me in just fine.
Anyway, thought I'd mention it.
2. Make sure that your account has a big enough quota
- Go to https://inkscape.org/user/ and hover over the "Upload Quota"
bar, you will only see 10MB if you are a normal user at this time. If
you do not see a 1GB quota then you need to contact a website admin (me)
to put you into the releases group with the larger quota.
Looks like I'm at only 10MB, so I'll need increased. I upload about
100MB of source packages for each pre-release and release so I expect
even 1GB will go quick.
3. Make sure you have a public gpg key recorded.
- Go to https://inkscape.org/user/edit/ and fill in the right boxes,
the GPG Public Key box is expecting a pasted public key (not private
key!) and hit submit when done.
Done
4. Make a folder for your releases in your 'InkSpace'.
- Go to https://inkscape.org/gallery/new/ and fill in the name of the
folder you want to use. This folder is only for your own organisation
and won't be seen by users.
5. Upload your released file
- Go to https://inkscape.org/user/ and drag your file to the new
gallery folder created above. The upload may take some time but you
should be able to see a progress bar as it uploads. (if you don't have
javascript enabled, you can click on the folder and then click add and
follow the manual form)
Any way to get multiple file upload?
I'm uploading Inkscape source packages, so none of the Categories fit
exactly. I stuck it in Inkscape Build, but it's not a build. Perhaps
'Inkscape Package' would be a better categorization?
Is there an API I could use to automate the upload of these files? With
Wayland and Cairo, they have a release.sh script which does make dist,
signs stuff, and uploads the tarballs to the central server. It saves a
huge amount of time to have a one-button-release.
6. Enter all the details
- Go into your folder and click on the newly uploaded item. It should
have a red border indicating it's not yet published (if you used the
drag+drop method)
- Going into the editor section you should be able to fill in the
title for the released file.
- Paste in the release notes into the description.
Hmm, I wonder if we could do this better? A link to the actual release
notes posted to the website would be better than re-pasting the text
here, wouldn't it?
- Select 'Releases' from the category drop down.
- Attach the sig file from your detached.
- Select 'GPLv2' from the Licenses drop down.
- Check 'Mirror' checkbox (if you have this)
- Check 'Visible' checkbox
Submit this form.
What is 'External Link' about? There was a 'Publicly Visible' checkbox
but no 'Mirrored' checkbox.
7. Verify and copy link
- If everything's gone well you should now see your released file with
a green padlock indicating the gpg signature has been verified against
your account public key.
- Download the release by clicking on the down-arrow icon. Confirm
it's the file you intended.
- Copy this download link.
8. Link from the downloads page.
- For this step you will need CMS editor access or pass this task onto
a website editor and/or translator.
- Edit the downloads pages for the right OS and update with the right
version, release and other details as you would want it to be presented
to users. Add the copied link into the right place.
- Save /and/ then hit the blue publish button.
Congratulations, you've uploaded, released and published your release
file. Let the website administrator (me) know if you have any difficulty
with this process.
Best Regards, Martin Owens
Thanks for setting this up Martin!
Bryce
11:21 p.m.
On 18 January 2015 at 04:24, Bryce Harrington <bryce@...961...> wrote:
I attempted to log in this way, but got an error,
CSRF verification failed. Request aborted.
This is a very annoying bug. When the site is requested, it doesn't
set a csrf token for the first home page and I have /no/ idea why not.
There isn't much online about it.
I've set a CSRF secure token option in the settings to see if it
helps. Anyone let me know if you see this error.
Looks like I'm at only 10MB, so I'll need increased. I
upload about
100MB of source packages for each pre-release and release so I expect
even 1GB will go quick.
I tried to add a 10GB quota, the number field maxed out at 2GB, must
be a db limit. I've changed the code for the next version to use KiB
for the quota setting instead of bytes.
Any way to get multiple file upload?
Drag multiple files? (works here)
I'm uploading Inkscape source packages, so none of the Categories
fit
exactly. I stuck it in Inkscape Build, but it's not a build. Perhaps
'Inkscape Package' would be a better categorization?
Aye, suv asked me to change it from release to build. But I guess
package makes just as much sense. This ok with you suv?
Is there an API I could use to automate the upload of these files?
The drag and drop makes an ajax call, you can use that if you like.
But it doesn't set descriptions or other settings, just uploads the
files. Plus the complexity of getting some authorised cookies and it's
not ideal for a script. Some sort of REST api could be added to the
feature wishlist on launchpad bugs. Be sure to mention how you'd like
it to work.
Hmm, I wonder if we could do this better? A link to the actual
release
notes posted to the website would be better than re-pasting the text
here, wouldn't it?
It depends here. We may want the website release notes to be more user
orientated and the readme notes more developer. I figured this and
added the readme download view so you could say:
https://inkscape.org/en/gallery/item/3044/readme.txt and scripts might
be able to just grab that text for their own uses.
But it's up to you, let me know. Use the external link to link to more
information.
What is 'External Link' about? There was a 'Publicly
Visible' checkbox
but no 'Mirrored' checkbox.
Mirrored is only available to people with the mirror permission. I've
added it for your release master's group.
Thanks for setting this up Martin!
Happy to see it being tested! Thanks bryce!
Best Regards, Martin Owens
11:32 p.m.
On 2015-01-18 15:21 (+0100), Martin Owens wrote:
> I'm uploading Inkscape source packages, so none of the
Categories fit
> exactly. I stuck it in Inkscape Build, but it's not a build. Perhaps
> 'Inkscape Package' would be a better categorization?
Aye, suv asked me to change it from release to build. But I guess
package makes just as much sense. This ok with you suv?
Probably we need several tags (that last time I was asked to test
uploading, it was for OS X _devel_ snapshot builds (trunk, 0.91.x),
which at the time seemed wrong to me to be labelled 'release' IIRC
(still would be, if there are plans to host those too on inkscape.org)).
Didn't check what is available right now.
Regards, V
1:36 a.m.
OK... so in looking at things, I think releases need to be treated as
EXTRA special. What I mean by that is that they need to have a
straightforward and obvious human-readable url. This gallery item with
a non-related number (as in not related to the release) is incredibly
odd and off-putting. I really think that for releases the url should
be along the lines of
https://inkscape.org/en/download/0.91.x/Inkscape-0.91.0.exe and not
https://inkscape.org/en/gallery/item/3680/download/ (the first url is
NOT REAL, the second is for a prerelease tarball which you probably
don't need)
The current gallery item naming will probably cause more "alert" users
to be overly cautious. I'm mainly bringing it up because when I saw
the package urls from what bryce had uploaded my first thought was "I
don't know what is at the other end of that url"... I'm not saying you
ever really know or that you can't get re-directed away from what it
says is your destination, just that it seems far more questionable. If
I was unfamiliar with a project and saw a download that didn't point
to an end file or an FTP directory, chances are I either wouldn't
follow it or would otherwise seriously question why they're doing it
that way and send an email.
Cheers,
Josh
On Sun, Jan 18, 2015 at 6:32 AM, su_v <suv-sf@...58...> wrote:
On 2015-01-18 15:21 (+0100), Martin Owens wrote:
>> I'm uploading Inkscape source packages, so none of the Categories fit
>> exactly. I stuck it in Inkscape Build, but it's not a build. Perhaps
>> 'Inkscape Package' would be a better categorization?
>
> Aye, suv asked me to change it from release to build. But I guess
> package makes just as much sense. This ok with you suv?
Probably we need several tags (that last time I was asked to test
uploading, it was for OS X _devel_ snapshot builds (trunk, 0.91.x),
which at the time seemed wrong to me to be labelled 'release' IIRC
(still would be, if there are plans to host those too on inkscape.org)).
Didn't check what is available right now.
Regards, V
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
3:37 a.m.
This is certainly a bug report Josh ;-)
It is possible to create a redirection, the problem is that we have this
download url so we can track a count. If you want untracked file
downloads, those are already available in
the /media/resource/file/$filename urls.
Martin,
On Mon, 2015-01-19 at 08:36 -0800, Josh Andler wrote:
The current gallery item naming will probably cause more
"alert" users
to be overly cautious. I'm mainly bringing it up because when I saw
the package urls from what bryce had uploaded my first thought was "I
don't know what is at the other end of that url"... I'm not saying you
ever really know or that you can't get re-directed away from what it
says is your destination, just that it seems far more questionable. If
I was unfamiliar with a project and saw a download that didn't point
to an end file or an FTP directory, chances are I either wouldn't
follow it or would otherwise seriously question why they're doing it
that way and send an email.
2:54 a.m.
Martin,
So, can't we create human friendly urls that redirect to the download
url so they still get tracked?
Cheers,
Josh
On Mon, Jan 19, 2015 at 10:37 AM, Martin Owens <doctormo@...400...> wrote:
This is certainly a bug report Josh ;-)
It is possible to create a redirection, the problem is that we have this
download url so we can track a count. If you want untracked file
downloads, those are already available in
the /media/resource/file/$filename urls.
Martin,
On Mon, 2015-01-19 at 08:36 -0800, Josh Andler wrote:
> The current gallery item naming will probably cause more "alert" users
> to be overly cautious. I'm mainly bringing it up because when I saw
> the package urls from what bryce had uploaded my first thought was "I
> don't know what is at the other end of that url"... I'm not saying you
> ever really know or that you can't get re-directed away from what it
> says is your destination, just that it seems far more questionable. If
> I was unfamiliar with a project and saw a download that didn't point
> to an end file or an FTP directory, chances are I either wouldn't
> follow it or would otherwise seriously question why they're doing it
> that way and send an email.
4:21 a.m.
On Tue, 2015-01-20 at 09:54 -0800, Josh Andler wrote:
So, can't we create human friendly urls that redirect to the
download
url so they still get tracked?
http://bazaar.launchpad.net/~inkscape-webadmin/inkscape-web/inkscape-web/...
Of course, you'd have seen the patch go in if you had made a bug
report :-P
The website team is growing, we're now at the point where we must be
more insistent that problems and feature requests be recorded as bugs
going forwards.
Thanks everyone.
Martin,
5:04 a.m.
Cool beans! I will try to remember to search the web tracker first
with issues before reporting things directly to you or bringing it up
on the list. Kudos to the growth! :)
Cheers,
Josh
On Tue, Jan 20, 2015 at 11:21 AM, Martin Owens <doctormo@...400...> wrote:
On Tue, 2015-01-20 at 09:54 -0800, Josh Andler wrote:
> So, can't we create human friendly urls that redirect to the download
> url so they still get tracked?
http://bazaar.launchpad.net/~inkscape-webadmin/inkscape-web/inkscape-web/...
Of course, you'd have seen the patch go in if you had made a bug
report :-P
The website team is growing, we're now at the point where we must be
more insistent that problems and feature requests be recorded as bugs
going forwards.
Thanks everyone.
Martin,
4:54 a.m.
On 2015-01-19 17:36 (+0100), Josh Andler wrote:
OK... so in looking at things, I think releases need to be treated
as
EXTRA special. What I mean by that is that they need to have a
straightforward and obvious human-readable url. This gallery item with
a non-related number (as in not related to the release) is incredibly
odd and off-putting. I really think that for releases the url should
be along the lines of
https://inkscape.org/en/download/0.91.x/Inkscape-0.91.0.exe and not
https://inkscape.org/en/gallery/item/3680/download/ (the first url is
NOT REAL, the second is for a prerelease tarball which you probably
don't need)
The current gallery item naming will probably cause more "alert" users
to be overly cautious. I'm mainly bringing it up because when I saw
the package urls from what bryce had uploaded my first thought was "I
don't know what is at the other end of that url"... I'm not saying you
ever really know or that you can't get re-directed away from what it
says is your destination, just that it seems far more questionable. If
I was unfamiliar with a project and saw a download that didn't point
to an end file or an FTP directory, chances are I either wouldn't
follow it or would otherwise seriously question why they're doing it
that way and send an email.
Sharing the same concerns here.
Regards, V
5:44 p.m.
Hello Martin,
I uploaded the inkscape pre4 compiled for windows here
https://inkscape.org/en/gallery/5540/
Best regards, Adib.
--
On Wed, Dec 31, 2014 at 11:26 PM, Martin Owens <doctormo@...400...> wrote:
Hi Developers,
I'm going to try and be as verbose as possible about the procedure to
upload your own release to inkscape.org, I need you to perform this task
if you package any of our release packages because a) it's good practice
and b) packages will be signed with your gpg key and it'd be an odd
world where I could do that for you. :-)
Releasing on inkscape.org:
1. Make sure you have a user account on inkscape.org
- Go to https://inkscape.org and look in the top right of the page and
note your logged in status, use the links provided in the drop down to
log in or register an account.
2. Make sure that your account has a big enough quota
- Go to https://inkscape.org/user/ and hover over the "Upload Quota"
bar, you will only see 10MB if you are a normal user at this time. If
you do not see a 1GB quota then you need to contact a website admin (me)
to put you into the releases group with the larger quota.
3. Make sure you have a public gpg key recorded.
- Go to https://inkscape.org/user/edit/ and fill in the right boxes,
the GPG Public Key box is expecting a pasted public key (not private
key!) and hit submit when done.
4. Make a folder for your releases in your 'InkSpace'.
- Go to https://inkscape.org/gallery/new/ and fill in the name of the
folder you want to use. This folder is only for your own organisation
and won't be seen by users.
5. Upload your released file
- Go to https://inkscape.org/user/ and drag your file to the new
gallery folder created above. The upload may take some time but you
should be able to see a progress bar as it uploads. (if you don't have
javascript enabled, you can click on the folder and then click add and
follow the manual form)
6. Enter all the details
- Go into your folder and click on the newly uploaded item. It should
have a red border indicating it's not yet published (if you used the
drag+drop method)
- Going into the editor section you should be able to fill in the
title for the released file.
- Paste in the release notes into the description.
- Select 'Releases' from the category drop down.
- Attach the sig file from your detached.
- Select 'GPLv2' from the Licenses drop down.
- Check 'Mirror' checkbox (if you have this)
- Check 'Visible' checkbox
Submit this form.
7. Verify and copy link
- If everything's gone well you should now see your released file with
a green padlock indicating the gpg signature has been verified against
your account public key.
- Download the release by clicking on the down-arrow icon. Confirm
it's the file you intended.
- Copy this download link.
8. Link from the downloads page.
- For this step you will need CMS editor access or pass this task onto
a website editor and/or translator.
- Edit the downloads pages for the right OS and update with the right
version, release and other details as you would want it to be presented
to users. Add the copied link into the right place.
- Save /and/ then hit the blue publish button.
Congratulations, you've uploaded, released and published your release
file. Let the website administrator (me) know if you have any difficulty
with this process.
Best Regards, Martin Owens
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is
your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
10:20 p.m.
On Tue, 2015-01-20 at 09:44 +0100, theadib wrote:
I uploaded the inkscape pre4 compiled for windows here
https://inkscape.org/en/gallery/5540/
Once you have uploaded some files, you'll need to edit them to publish
them for public view. I can't actually see anything at the link because
the items haven't been edited yet.
Martin,
7:10 a.m.
I modified them (checked the public visible option).
Do you see it now?
Cheers, Adib.
--
On Tue, Jan 20, 2015 at 2:20 PM, Martin Owens <doctormo@...400...> wrote:
On Tue, 2015-01-20 at 09:44 +0100, theadib wrote:
> I uploaded the inkscape pre4 compiled for windows here
> https://inkscape.org/en/gallery/5540/
Once you have uploaded some files, you'll need to edit them to publish
them for public view. I can't actually see anything at the link because
the items haven't been edited yet.
Martin,
5:06 p.m.
On Wed, Dec 31, 2014 at 05:26:20PM -0500, Martin Owens wrote:
Hi Developers,
I'm going to try and be as verbose as possible about the procedure to
upload your own release to inkscape.org, I need you to perform this task
if you package any of our release packages because a) it's good practice
and b) packages will be signed with your gpg key and it'd be an odd
world where I could do that for you. :-)
I've pasted these directions to the CreatingDists page:
http://wiki.inkscape.org/wiki/index.php/Creating_Inkscape_distributions#U...
Improvements to these directions are appreciated!
Releasing on inkscape.org:
1. Make sure you have a user account on inkscape.org
- Go to https://inkscape.org and look in the top right of the page and
note your logged in status, use the links provided in the drop down to
log in or register an account.
2. Make sure that your account has a big enough quota
- Go to https://inkscape.org/user/ and hover over the "Upload Quota"
bar, you will only see 10MB if you are a normal user at this time. If
you do not see a 1GB quota then you need to contact a website admin (me)
to put you into the releases group with the larger quota.
3. Make sure you have a public gpg key recorded.
- Go to https://inkscape.org/user/edit/ and fill in the right boxes,
the GPG Public Key box is expecting a pasted public key (not private
key!) and hit submit when done.
4. Make a folder for your releases in your 'InkSpace'.
- Go to https://inkscape.org/gallery/new/ and fill in the name of the
folder you want to use. This folder is only for your own organisation
and won't be seen by users.
5. Upload your released file
- Go to https://inkscape.org/user/ and drag your file to the new
gallery folder created above. The upload may take some time but you
should be able to see a progress bar as it uploads. (if you don't have
javascript enabled, you can click on the folder and then click add and
follow the manual form)
6. Enter all the details
- Go into your folder and click on the newly uploaded item. It should
have a red border indicating it's not yet published (if you used the
drag+drop method)
- Going into the editor section you should be able to fill in the
title for the released file.
- Paste in the release notes into the description.
- Select 'Releases' from the category drop down.
- Attach the sig file from your detached.
- Select 'GPLv2' from the Licenses drop down.
- Check 'Mirror' checkbox (if you have this)
- Check 'Visible' checkbox
Submit this form.
7. Verify and copy link
- If everything's gone well you should now see your released file with
a green padlock indicating the gpg signature has been verified against
your account public key.
- Download the release by clicking on the down-arrow icon. Confirm
it's the file you intended.
- Copy this download link.
8. Link from the downloads page.
- For this step you will need CMS editor access or pass this task onto
a website editor and/or translator.
- Edit the downloads pages for the right OS and update with the right
version, release and other details as you would want it to be presented
to users. Add the copied link into the right place.
- Save /and/ then hit the blue publish button.
Congratulations, you've uploaded, released and published your release
file. Let the website administrator (me) know if you have any difficulty
with this process.
Best Regards, Martin Owens
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
3044
days inactive
3072
days old
inkscape-devel@lists.inkscape.org
13 comments
6 participants
participants (6)
-
Bryce Harrington -
Josh Andler -
Martin Owens -
su_v -
the Adib -
theadib