www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-12683) Moving binary bits between users and support resources -- support packages
Date Sat, 08 Oct 2016 18:43:20 GMT

    [ https://issues.apache.org/jira/browse/INFRA-12683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15558501#comment-15558501

Shawn Heisey commented on INFRA-12683:

On the mailing list:  At this time, I can't say whether the solr-user@lucene.a.o mailing list
is misbehaving where attachments are concerned, because I do not know what the configured
attachment policy for the list is.  We do seem to have hit or miss luck with getting attachments
that users send to the list ... but I suspect that the list is probably behaving exactly as
it is configured.  Can someone summarize what the configured policy is?

> Moving binary bits between users and support resources -- support packages
> --------------------------------------------------------------------------
>                 Key: INFRA-12683
>                 URL: https://issues.apache.org/jira/browse/INFRA-12683
>             Project: Infrastructure
>          Issue Type: New Feature
>          Components: Mailing Lists, Website
>            Reporter: Shawn Heisey
>            Priority: Minor
> I'm a committer on lucene-solr.  I have opened SOLR-9587 as an idea I hope to implement.
> This idea contains certain challenges that I wish to discuss with INFRA before I get
started.  Once a user creates a support package, they will need to have a reliable conduit
by which they can get that information to those who can help with their problem, mostly on
the solr-user mailing list and some IRC channels that we maintain on freenode.
> One idea, if we can mostly keep the packages below 1MB in size, is the public-facing
apache paste bucket site, http://apaste.info ... but potentially thousands of packages with
an average size of hundreds of kilobytes appearing in that database in a short amount of time
is probably NOT a good thing.
> A well-optimized and dedicated web service for handling such packages is another idea,
but I have no idea what that would entail, and again, it's another burden on Infra, and probably
too much to ask if lucene-solr is the only project using such a resource.
> Asking users to use public resources like dropbox is compelling, and that will probably
be how we start out with this, but a headache-free process for end users would be very nice
to have.
> If infra DOES end up making a service, we can reduce the load by incorporating fairly
aggressive and non-optional expiration dates for all data.
> The last idea to discuss is attachments on our mailing list.  We have had very much mixed
luck with attachments on our list in the past, and would like to understand exactly what the
attachment rules are on solr-user@lucene.a.o ... and what infra really thinks about the idea
of these support packages traversing the list.  I do think attachments should NOT get stored
in the mail archives, regardless of what else happens.

This message was sent by Atlassian JIRA

View raw message