Thanks Gus, for providing the clear pros/cons list and posing an objection.
I welcome constructive criticism that strengthens our discussion.
Among the informative list, I'd highlight a new perspective I haven't seen
so far (and honestly, I haven't considered): Security issues that are
visible to
I think both tools have their merits and drawbacks
What I like about Jira:
- It has ample room and configuration for issue metadata and
customizable workflows and in general a deep feature set
- It has user roles, PMC members can see security issues that are hidden
from the world...
I *think* it would be possible to write an IntervalsSource implementation that
took opening and closing tags, and did the right thing here - as you say, a
standard `contains` will try and minimise things, but you could write something
that attempted to match an opening tag with its
+1 MarkLogic is an excellent product. This Lux thing was inspired by it.
On Fri, May 6, 2022 at 11:29 AM Walter Underwood wrote:
>
> If you need to search XML, consider MarkLogic. It is a very full-featured
> database and search engine based on XML.
>
> https://www.marklogic.com
>
> Disclaimer:
If you need to search XML, consider MarkLogic. It is a very full-featured
database and search engine based on XML.
https://www.marklogic.com
Disclaimer: I worked there for a couple of years ten years ago. But I’ve been
inside that product and it is non-muggle technology.
wunder
Walter
On Thu, May 5, 2022 at 7:56 AM Robert Muir wrote:
As far as replies, in github I highlight the part of the thing i want
> to reply to, and press 'r' key on my keyboard. it quotes it and
> everything. Really convenient to me.
>
Whoa, thank you!! I had no idea GitHub has such extensive keyboard
Many years ago I had started this Lux project that was designed to
build an XML-aware index using Solr; see
https://github.com/msokolov/lux/tree/master/src/main/java/lux/index/analysis
for the analysis chain I used. Maybe you'll find something useful in
this project? It's dormant for years, and
Hi Devs!
I found intervals quite nice and natural for retrieving scoped data
(thanks, Alan!):
foo stuff bar
I.containing(I.ordered(I.term(""), I.term("")),
I.unordered(I.term("bar"), I.term("foo")));
It works like a charm until it encounter ill nested tags:
foo bug bar
Due
Thanks, Jan for your suggestion - I'd defer the discussion for the options
to contribute from outside GitHub for now, but we'll come back to this
later and we'll find some good ways (if the coming possible vote is passed).
> BWT: All issues, both in JIRA and GitHub are readable to the public
For code changes, patch files in Jira used to be the only option. Over the
years, this is almost completely replaced by PRs, but we still leave the door
open for patch in JIRA.
We could apply the same principle here: Don't shut down JIRA, but change
documentation so that GitHub issues is
10 matches
Mail list logo
